AI agents use create_presentation to create or update resources in Google Slides — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Slides environment.
Creating a new presentation is a reversible write operation—it adds a new document to the user's account but does not delete, execute code, or commit financial transactions. The severity is medium because creating unwanted presentations could clutter a user's account and consume storage quota, but the action is reversible through deletion. Confidence is high because the intent and effect are explicit and unambiguous.
From the tool's definition Tool name is 'create_presentation' and description states 'Create a new Google Slides presentation'. This creates new data (a presentation resource) in the user's Google Slides account.
Documented attack patterns abuse exactly the kind of access create_presentation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Slides, and nothing reaches the server without passing your rules. This is the rule we recommend for create_presentation:
{
"version": "1",
"default": "deny",
"tools": {
"create_presentation": {
"limits": [
{
"counter": "create_presentation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_presentation 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.
Create a new Google Slides presentation. It is categorised as a Write tool in the Google Slides MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Slides MCP server in PolicyLayer and add a rule for create_presentation: 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 Google Slides. Nothing to install.
create_presentation 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 create_presentation 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 create_presentation. 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.
create_presentation is provided by the Google Slides MCP server (matteoantoci/google-slides-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Slides, 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.
5 Google Slides tools catalogued and risk-classified — across an index of 43,000+ MCP servers.