Searches through the Openfort documentation for the given phrase
AI agents call search-documentation to retrieve information from Openfort MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Searching documentation is a pure read operation that retrieves information without modifying, deleting, or executing any system operations. Even in the context of a wallet infrastructure platform, querying documentation poses minimal risk as it only returns static reference material.
From the tool's definition Tool name is 'search-documentation' and description states it 'Searches through the Openfort documentation for the given phrase' — this is a query operation with no side effects.
Attacks that exploit this kind of access
Searches through the Openfort documentation for the given phrase. It is categorised as a Read tool in the Openfort MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Openfort MCP Server 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 Openfort MCP Server. 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 Openfort MCP Server MCP server (openfort-xyz/-deprecated-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 →