Fetch full content of a document by its ID (file path or repository URL)
AI agents call fetch to retrieve information from Codebase Insights MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a retrieval operation that queries and returns document content based on an identifier. It has no side effects, does not modify data, execute code, delete resources, or commit financial transactions. The scope is limited to reading existing codebase files from already-accessible repositories. Risk is low as long as repository access controls are properly enforced upstream.
From the tool's definition Tool name 'fetch' and description 'Fetch full content of a document by its ID (file path or repository URL)' indicate retrieval of file/document content with no modification capability.
Attacks that exploit this kind of access
Fetch full content of a document by its ID (file path or repository URL). It is categorised as a Read tool in the Codebase Insights MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Codebase Insights MCP Server MCP server in PolicyLayer and add a rule for fetch: 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 Codebase Insights MCP Server. Nothing to install.
fetch 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 fetch 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 fetch. 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.
fetch is provided by the Codebase Insights MCP Server MCP server (llanterme/codebase-insights-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 →