Search for code examples and snippets in documentation
AI agents call search_code_blocks to retrieve information from MkDocs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only searches and retrieves code examples from documentation. It does not execute code, modify data, delete content, or perform any irreversible actions. It is analogous to a grep or search function over static documentation content. The blast radius of misuse is minimal - an AI could only retrieve information that is already publicly documented.
From the tool's definition Tool description states 'Search for code examples and snippets in documentation' - this is purely a retrieval operation with no side effects. The name 'search_code_blocks' and the server context (documentation access) confirm this is a query operation.
Attacks that exploit this kind of access
Search for code examples and snippets in documentation. It is categorised as a Read tool in the MkDocs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MkDocs MCP Server MCP server in PolicyLayer and add a rule for search_code_blocks: 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 MkDocs MCP Server. Nothing to install.
search_code_blocks 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 search_code_blocks 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 search_code_blocks. 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.
search_code_blocks is provided by the MkDocs MCP Server MCP server (robmatesick/mkdocs-mcp-example). 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 →