AI agents call docs_list_packages to retrieve information from Docs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure information-retrieval tool that enumerates available documentation packages and their properties. It has no capability to modify, delete, execute code, or affect external systems. The blast radius of misuse is negligible—an agent can only discover what packages are installed and their versions.
From the tool's definition Tool lists package metadata (name, version, source, file count) without modifying, deleting, or executing anything. Description explicitly states 'List every @particle-academy/* package', which is a retrieval operation with no side effects.
Attacks that exploit this kind of access
List every @particle-academy/* (and other scanned) package that has docs available, with name, version, source (node_modules vs workspace), and file count. It is categorised as a Read tool in the Docs MCP Server, which means it retrieves data without modifying state.
Register the Docs MCP server in PolicyLayer and add a rule for docs_list_packages: 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 Docs. Nothing to install.
docs_list_packages 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_list_packages 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_list_packages. 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_list_packages is provided by the Docs MCP server (particle-academy/docs-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 →