Apply multiple slide operations (insert/replace/delete/move) to a Marp file in a single file read/write cycle.
AI agents use batch_manage_slides 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.
While this tool includes delete operations, it operates on slide content within a presentation file that can be recovered through version control or undo mechanisms typical of document editing workflows. The primary purpose is reversible modification (insert, replace, move) of presentation slides. If the delete operation were truly permanent without recovery options, this would be Destructive.
From the tool's definition Tool description explicitly states it performs multiple slide operations including 'insert/replace/delete/move' on a Marp file.
Documented attack patterns abuse exactly the kind of access batch_manage_slides 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 batch_manage_slides:
{
"version": "1",
"default": "deny",
"tools": {
"batch_manage_slides": {
"limits": [
{
"counter": "batch_manage_slides_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} batch_manage_slides 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.
Apply multiple slide operations (insert/replace/delete/move) to a Marp file in a single file read/write cycle. 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 batch_manage_slides: 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.
batch_manage_slides 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 batch_manage_slides 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 batch_manage_slides. 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.
batch_manage_slides 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.