AI agents use generate_powerpoint to create or update resources in Slidespeak — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slidespeak environment.
This tool creates or generates PowerPoint files, which constitutes reversible data creation (Write category). It does not execute arbitrary code, delete data, or move money. Severity is medium because a misused tool could generate numerous unwanted presentations or embed malicious content in slides, but the effects are reversible (files can be deleted).
From the tool's definition Tool named 'generate_powerpoint' with server description stating 'Generate PowerPoint presentations using the Slidespeak API'. The tool creates presentation files, which are data artifacts.
Documented attack patterns abuse exactly the kind of access generate_powerpoint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Slidespeak, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_powerpoint:
{
"version": "1",
"default": "deny",
"tools": {
"generate_powerpoint": {
"limits": [
{
"counter": "generate_powerpoint_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_powerpoint 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.
generate_powerpoint. It is categorised as a Write tool in the Slidespeak MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slidespeak MCP server in PolicyLayer and add a rule for generate_powerpoint: 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 Slidespeak. Nothing to install.
generate_powerpoint 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_powerpoint 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_powerpoint. 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_powerpoint is provided by the Slidespeak MCP server (slidespeak/slidespeak-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Slidespeak, 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.
7 Slidespeak tools catalogued and risk-classified — across an index of 43,000+ MCP servers.