Answers to common questions about connecting and using Scrut MCP. Any Scrut user (admin, contributor, auditor) can connect Scrut MCP to their AI tool. Once connected, your AI assistant only sees what your existing Scrut role already lets you see. You don't need to configure separate MCP-specific permissions. If you're a partner or auditor with access to more than one workspace, your AI tool can reach every workspace you're already assigned to, and you can switch between them within the same session. Your new role applies automatically; No need to reconnect. Scrut MCP checks your user record and role on an ongoing basis, so a role change takes effect within a few minutes of being made in Scrut. Scrut MCP requests will fail if your Scrut account is deactivated. A deactivated user can't use Scrut MCP, just as they can't sign in to the Scrut platform. No. Each person connects with their own Scrut login, and there's no cap on how many users in your organization can connect or stay active at the same time. There's no fixed logout timeframe. Scrut MCP uses short-lived access tokens that your AI tool refreshes silently in the background, so you stay connected without re-entering credentials. You remain connected until you disconnect Scrut MCP from your AI tool, your sign-in grant expires or is revoked, or your Scrut account is deactivated. If any of these happen, the tool will prompt you to sign in again. Yes. Each AI tool gets its own independent sign-in. You can be connected to Claude, Cursor, and others simultaneously. Disconnecting one doesn't affect the others, and none of them affect your Scrut web session. No. You can change statuses, owners, and assignments only in Scrut. Scrut MCP can show you this information, but it cannot update it. Scrut MCP cannot: - Create or edit policies, controls, or tasks - Change statuses, owners, or assignments - Do user administration - Touch the vendor, risk, or people modules - See anything the signed-in user doesn't already have access to - Replace the Scrut platform itself Yes, as long as the application running the local model (e.g., Llama via Ollama) supports remote MCP servers with OAuth sign-in. However, response quality depends on the model’s tool-calling ability, so results may differ with smaller local models. Common use cases include frameworks, next audit dates, controls, policies, evidence, and continuous cloud tests, along with their status, owner, and mappings. Yes. You can upload a file and attach it to an existing evidence item. Scrut tracks every upload in its audit log, just as a human user's upload would be. Yes, Scrut logs all actions taken through Scrut MCP the same way it logs a human user's actions. For example, if user "John" has uploaded an evidence file via MCP, Scrut will display this audit log: "John uploaded \[evidence attachment name]." Yes. It can pull answers from your approved answer library or generate an answer from your knowledge base with complete references so you can verify the source. Yes, Scrut MCP can generate digests and status updates on demand, for example, a summary of what's outstanding ahead of an audit. Yes. Use the document content tool to pull the full text of one specific policy or evidence document when you need to quote or verify it. No. Scrut MCP can upload files and attach evidence, but it can't delete or overwrite anything that already exists in your compliance program. Yes. Scrut MCP provides a faster starting point for questionnaire responses, evidence filing, and status updates. It doesn't remove human review from evidence decisions or audit responses. No rate limits are enforced today, and you don't need to space out your prompts. It depends on the access you already have in Scrut. If your Scrut role includes cloud test remediation, Scrut MCP can use that same access to reach the infrastructure-as-code to suggest a fix. If your role doesn't include it, your AI tool won't have that access either, regardless of what you ask it to do. Tasks like asking questions, drafting questionnaire answers, and filing evidence don't need cloud or codebase access. No. Scrut remains your system of record for your compliance program. Scrut MCP brings that context into the AI tools you already work in; it doesn't move your compliance program anywhere else. Yes. It is available for all plans (Foundation, Growth, and Scale) You can do it yourself. For step-by-step instructions, see Connect Scrut MCP. No. Scrut MCP acts in your own Scrut role with the same access you already have on the platform. It doesn't grant your AI tool broader access. Yes. If a workspace has multiple entities configured, you can ask your AI assistant to filter artifacts, such as evidence, controls, or policies, by entity within that workspace. Entity access still follows the permissions you already have in Scrut. Yes. If you have access to multiple workspaces, for example, as a partner or auditor, you can switch between them within a single MCP session. You don't need to disconnect and reconnect for each workspace you want to review. Reach out to [support@scrut.io](mailto:support@scrut.io) or contact your CSM for further assistance.

FAQs: Scrut MCP