search_documentation
AI agents call search_documentation to retrieve information from Portable MCP Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs information retrieval without modifying data or executing arbitrary operations. Search operations are inherently read-only queries. Despite the empty description lowering confidence slightly, the clear naming and consistent context with sibling read-only tools strongly indicate Read category. Severity is low because retrieval of documentation poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'search_documentation' indicates querying/retrieving documentation; verb 'search' is a read operation.
Attacks that exploit this kind of access
search_documentation. It is categorised as a Read tool in the Portable MCP Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Portable MCP Toolkit MCP server in PolicyLayer and add a rule for search_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 Portable MCP Toolkit. Nothing to install.
search_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 search_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 search_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.
search_documentation is provided by the Portable MCP Toolkit MCP server (mjdevaccount/aistack-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 →