Scan a local repository folder and audit its AI context quality. Returns a score (0-100) across 7 dimensions: Architecture, Commands, Conventions, Off-limits, Testing, Deployment, Freshness. Also detects programming language, framework, file count, and total size.
AI agents call scan_repo to retrieve information from RepoMemory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
scan_repo performs reconnaissance and analysis of a codebase—a passive read operation. It retrieves and evaluates information (quality scores, language detection, file metrics) without modifying, executing, or deleting anything.
From the tool's definition Tool description states it 'scans' a repository and 'audits' its AI context quality, returning scores and metadata.
Attacks that exploit this kind of access
Scan a local repository folder and audit its AI context quality. Returns a score (0-100) across 7 dimensions: Architecture, Commands, Conventions, Off-limits, Testing, Deployment, Freshness. Also detects programming language, framework, file count, and total size. It is categorised as a Read tool in the RepoMemory MCP Server, which means it retrieves data without modifying state.
Register the RepoMemory MCP server in PolicyLayer and add a rule for 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 RepoMemory. Nothing to install.
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 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 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.
scan_repo is provided by the RepoMemory MCP server (praveenjayaprakash-jp/repomemory). 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 →