AI agents use export_pdf to create or update resources in Marp Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Marp Agent environment.
This tool creates a new PDF file from existing slide content. While it produces an output file, it is reversible (the PDF can be deleted or regenerated) and does not modify the source slides or system state irreversibly. It is a Write operation rather than Execute because it is a high-level export function with a well-defined purpose, not arbitrary code execution.
From the tool's definition Tool name 'export_pdf' and description 'Export slides to PDF format' indicate generation and output of a new file artifact.
Documented attack patterns abuse exactly the kind of access export_pdf gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Marp Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for export_pdf:
{
"version": "1",
"default": "deny",
"tools": {
"export_pdf": {
"limits": [
{
"counter": "export_pdf_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_pdf stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Export slides to PDF format. It is categorised as a Write tool in the Marp Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Marp Agent MCP server in PolicyLayer and add a rule for export_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 Marp Agent. Nothing to install.
export_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 export_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 export_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.
export_pdf is provided by the Marp Agent MCP server (iwamot/marp-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Marp Agent, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Marp Agent tools catalogued and risk-classified — across an index of 43,000+ MCP servers.