AI agents call get_requirements to retrieve information from Pdf Spec without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves normative requirements from ISO 32000-2 specification documents. It has no side effects—it does not create, modify, delete, execute code, or trigger external operations. It is purely informational extraction from static specification data, consistent with sibling tools like 'search_spec', 'get_section', and 'get_definitions' which are all Read category tools.
From the tool's definition Tool name 'get_requirements' and description 'Extract normative requirements' indicate data retrieval with no modification or execution. The verb 'extract' combined with context of reading from specification documents confirms read-only access pattern.
Attacks that exploit this kind of access
Extract normative requirements (shall/must/may) from the PDF specification (ISO 32000-2). It is categorised as a Read tool in the Pdf Spec MCP Server, which means it retrieves data without modifying state.
Register the Pdf Spec MCP server in PolicyLayer and add a rule for get_requirements: 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 Pdf Spec. Nothing to install.
get_requirements 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 get_requirements 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 get_requirements. 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.
get_requirements is provided by the Pdf Spec MCP server (shuji-bonji/pdf-spec-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 →