directory_to_pdf
AI agents use directory_to_pdf to create or update resources in Auto-Snap MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Auto-Snap MCP environment.
Based on the tool name and server context (which involves converting screenshots into PDFs), this tool likely reads files from a directory and writes/creates a new PDF document. This is a Write operation as it creates a new file. Confidence is low because the description is empty, so exact behavior is inferred from the name and sibling tools like 'convert_to_pdf'.
From the tool's definition Tool name 'directory_to_pdf' and server context involving screenshot capture and PDF conversion
Attacks that exploit this kind of access
directory_to_pdf. It is categorised as a Write tool in the Auto-Snap MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Auto-Snap MCP server in PolicyLayer and add a rule for directory_to_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 Auto-Snap MCP. Nothing to install.
directory_to_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 directory_to_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 directory_to_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.
directory_to_pdf is provided by the Auto-Snap MCP server (povedaaqui/auto-snap-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 →