Auto-generate an agenda slide from section slides (detected by CSS class) and insert it before the first section.
AI agents use generate_agenda 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.
This tool creates new content (an agenda slide) and modifies the presentation structure by inserting it at a specific location. This is a reversible modification operation consistent with Write category. The severity is medium because while the action modifies the presentation, it is automatic, deterministic, and reversible—an agent could regenerate or delete the agenda slide if needed.
From the tool's definition The tool performs auto-generation and insertion of a slide (agenda), which modifies the presentation structure. The description states it will 'insert it before the first section,' indicating a create/modify operation that changes the presentation.
Documented attack patterns abuse exactly the kind of access generate_agenda 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 generate_agenda:
{
"version": "1",
"default": "deny",
"tools": {
"generate_agenda": {
"limits": [
{
"counter": "generate_agenda_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} generate_agenda 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.
Auto-generate an agenda slide from section slides (detected by CSS class) and insert it before the first section. 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 generate_agenda: 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.
generate_agenda 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 generate_agenda 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 generate_agenda. 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.
generate_agenda 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.