get_repo_documentation
AI agents call get_repo_documentation to retrieve information from Code Expert MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves documentation from a codebase without modifying, deleting, or executing anything. It is a passive data retrieval operation with no side effects or destructive potential. The low severity reflects minimal risk even if misused—an AI agent calling this repeatedly could cause performance issues but cannot compromise data integrity, delete content, or trigger financial consequences.
From the tool's definition Tool name 'get_repo_documentation' indicates retrieval of documentation from a repository. Sibling tools like 'get_repo_file_content', 'get_repo_structure', and 'list_repos' are all read-only operations.
Attacks that exploit this kind of access
get_repo_documentation. It is categorised as a Read tool in the Code Expert MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Code Expert MCP Server MCP server in PolicyLayer and add a rule for get_repo_documentation: 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 Code Expert MCP Server. Nothing to install.
get_repo_documentation 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 get_repo_documentation 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 get_repo_documentation. 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.
get_repo_documentation is provided by the Code Expert MCP Server MCP server (lfnovo/code-expert-mcp). 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 →