close_pdf
AI agents use close_pdf to create or update resources in PDF Redaction MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PDF Redaction MCP Server environment.
Without a description, high uncertainty exists about exact behavior. However, in context of a PDF redaction server with tools like 'load_pdf' and 'save_redacted_pdf', 'close_pdf' most likely unloads a document from memory or state. This is a Write action (reversible state modification) rather than Read, since it modifies the server's loaded document state.
From the tool's definition Tool name 'close_pdf' with empty description suggests it closes/unloads a loaded PDF document, likely modifying the server's internal state by removing a reference to an open file.
Attacks that exploit this kind of access
close_pdf. It is categorised as a Write tool in the PDF Redaction MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PDF Redaction MCP Server MCP server in PolicyLayer and add a rule for close_pdf: 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 Redaction MCP Server. Nothing to install.
close_pdf is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the close_pdf 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 close_pdf. 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.
close_pdf is provided by the PDF Redaction MCP Server MCP server (marc-hanheide/redact_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 →