Search the local UserGate documentation index.
AI agents call search_docs 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 is a read-only operation that searches and retrieves documentation. It has no side effects, cannot modify data, execute code, delete information, or commit financial obligations. The blast radius of misuse is minimal—an agent could retrieve information it shouldn't have access to, but cannot cause operational damage.
From the tool's definition Tool name 'search_docs' and description 'Search the local UserGate documentation index' indicate a query operation that retrieves information from a documentation corpus without modifying or executing anything.
Attacks that exploit this kind of access
Search the local UserGate documentation index. 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_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 UserGate MCP. 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 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 →