Export a Marp markdown presentation to HTML, PDF, or PPTX using marp-cli.
AI agents use export_slide to create or update resources in Marp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Marp MCP Server environment.
The tool generates and writes presentation output files in multiple formats. While export itself doesn't delete data, it creates new artifacts and may overwrite existing files, making it a Write operation.
From the tool's definition Tool exports Marp presentations to file formats (HTML, PDF, PPTX) using marp-cli. Export operations create new files or overwrite existing ones, constituting data creation and modification.
Documented attack patterns abuse exactly the kind of access export_slide gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Marp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for export_slide:
{
"version": "1",
"default": "deny",
"tools": {
"export_slide": {
"limits": [
{
"counter": "export_slide_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} export_slide 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 a Marp markdown presentation to HTML, PDF, or PPTX using marp-cli. It is categorised as a Write tool in the Marp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Marp MCP Server MCP server in PolicyLayer and add a rule for export_slide: 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 MCP Server. Nothing to install.
export_slide 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_slide 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_slide. 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_slide is provided by the Marp MCP Server MCP server (masaki39/marp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Marp MCP Server, 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.
11 Marp MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.