AI agents call docs.install to retrieve information from Ngsrv without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and returns static documentation (install commands and configuration snippets). It has no side effects, does not modify any state, and cannot cause harm if misused beyond leaking install instructions.
From the tool's definition Return ngsrv CLI install commands and MCP client configuration snippets
Attacks that exploit this kind of access
Return ngsrv CLI install commands and MCP client configuration snippets. It is categorised as a Read tool in the Ngsrv MCP Server, which means it retrieves data without modifying state.
Register the Ngsrv MCP server in PolicyLayer and add a rule for docs.install: 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 Ngsrv. Nothing to install.
docs.install 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 docs.install 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 docs.install. 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.
docs.install is provided by the Ngsrv MCP server (ngsrv/ngsrv-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 →