AI agents call doc to retrieve information from Python without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool generates documentation (read-like analysis output) and returns metrics (warning count). It has no side effects on the codebase, does not execute arbitrary code, and does not modify, delete, or create persistent data. This is a safe analytical/reporting operation similar to linting. Severity is low because misuse would only produce verbose or unwanted documentation output, not damage or compromise systems.
From the tool's definition Tool description states it 'Generates Rust documentation and returns structured output with warning count' — a documentation generation and reporting operation with no data modification, deletion, or external command execution.
Attacks that exploit this kind of access
Generates Rust documentation and returns structured output with warning count. It is categorised as a Read tool in the Python MCP Server, which means it retrieves data without modifying state.
Register the Python MCP server in PolicyLayer and add a rule for doc: 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 Python. Nothing to install.
doc 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 doc 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 doc. 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.
doc is provided by the Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
doc is one line of Python's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →