Search for sections in the MCP specification by keyword and return anchor links
AI agents call find_section to retrieve information from MCP SpecNavigator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search query against static specification documentation and returns results (anchor links). It has no side effects, cannot modify data, execute commands, or affect external systems. It is purely informational retrieval, fitting the Read category with low severity since misuse would only affect information access, not data integrity or system state.
From the tool's definition Tool description states 'Search for sections in the MCP specification by keyword and return anchor links' — a read-only operation that retrieves and returns existing specification data without modification, deletion, or execution of code.
Attacks that exploit this kind of access
Search for sections in the MCP specification by keyword and return anchor links. It is categorised as a Read tool in the MCP SpecNavigator MCP Server, which means it retrieves data without modifying state.
Register the MCP SpecNavigator MCP server in PolicyLayer and add a rule for find_section: 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 MCP SpecNavigator. Nothing to install.
find_section 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 find_section 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 find_section. 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.
find_section is provided by the MCP SpecNavigator MCP server (kayaozkur/mcp-server-specnavigator). 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 →