AI agents call codebrain_scan_repo to retrieve information from CodeBrain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Scanning a repository typically involves reading and analyzing code structure, dependencies, or metadata without modifying data. Given the context of a code generation server and the presence of 'codebrain_scan_file' among siblings, this is best classified as a Read operation with low blast radius.
From the tool's definition Tool name 'codebrain_scan_repo' indicates a scanning/analysis operation. The sibling tool 'codebrain_scan_file' on a code analysis server suggests read-only introspection of repository contents. The description is empty, reducing confidence.
Attacks that exploit this kind of access
codebrain_scan_repo. It is categorised as a Read tool in the CodeBrain MCP Server, which means it retrieves data without modifying state.
Register the CodeBrain MCP server in PolicyLayer and add a rule for codebrain_scan_repo: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches CodeBrain. Nothing to install.
codebrain_scan_repo is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the codebrain_scan_repo rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for codebrain_scan_repo. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
codebrain_scan_repo is provided by the CodeBrain MCP server (tschonsen/codebrain). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →