Analyze a repository to understand its structure, dependencies, and git history. Run this first before asking questions.
AI agents call analyze_repo to retrieve information from Repo Therapist without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing repository data (structure, dependencies, git history) to build a knowledge base for querying. It has no side effects—it does not modify code, execute scripts, delete files, or trigger external operations. The output is informational analysis used to support subsequent queries. This is a classic Read operation.
From the tool's definition Tool performs analysis and understanding of repository structure, dependencies, and git history with no modification capabilities.
Attacks that exploit this kind of access
Analyze a repository to understand its structure, dependencies, and git history. Run this first before asking questions. It is categorised as a Read tool in the Repo Therapist MCP Server, which means it retrieves data without modifying state.
Register the Repo Therapist MCP server in PolicyLayer and add a rule for analyze_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 Repo Therapist. Nothing to install.
analyze_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 analyze_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 analyze_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.
analyze_repo is provided by the Repo Therapist MCP server (salman-arefin74/repo-therapist). 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 →