Search the local UserGate index at section/chunk granularity.
AI agents call search_doc_sections to retrieve information from UserGate MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information from a local documentation index without creating, modifying, deleting, or executing any operations. It is a straightforward search function that returns query results, posing minimal risk even if misused by an agent—the worst outcome would be retrieving unintended information. The offline-first, documentation-focused context further confirms this is a read-only operation.
From the tool's definition Tool performs 'Search the local UserGate index at section/chunk granularity' with no modification, deletion, or execution capabilities described. The verb 'search' and the passive retrieval nature of querying an index align with data retrieval operations.
Attacks that exploit this kind of access
Search the local UserGate index at section/chunk granularity. It is categorised as a Read tool in the UserGate MCP MCP Server, which means it retrieves data without modifying state.
Register the UserGate MCP server in PolicyLayer and add a rule for search_doc_sections: 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 UserGate MCP. Nothing to install.
search_doc_sections 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_doc_sections 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_doc_sections. 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_doc_sections is provided by the UserGate MCP server (neonsummit/usergate-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 →