Search through internal documentation. Returns relevant documents based on query, category, and tags.
AI agents call search-docs to retrieve information from CHECK-MODULE 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 pure retrieval operation with no side effects. It queries internal documentation and returns results without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could over-search or retrieve sensitive internal docs, but cannot change state or trigger actions.
From the tool's definition Tool performs search and returns matching documents. The description states it 'Search[es] through internal documentation' and 'Returns relevant documents based on query, category, and tags' with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access search-docs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CHECK-MODULE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search-docs:
{
"version": "1",
"default": "deny",
"tools": {
"search-docs": {}
}
}search-docs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search through internal documentation. Returns relevant documents based on query, category, and tags. It is categorised as a Read tool in the CHECK-MODULE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CHECK-MODULE MCP Server MCP server in PolicyLayer and add a rule for search-docs: 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 CHECK-MODULE MCP Server. Nothing to install.
search-docs 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-docs 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-docs. 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-docs is provided by the CHECK-MODULE MCP Server MCP server (muhammedehab35/check-module-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CHECK-MODULE MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 CHECK-MODULE MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.