create_presentation
Creates a new Google Slides presentation and returns it (presentationId, revisionId, pageSize, the initial title slide with its object ids, layouts and masters). The API honors only the title at creation — add slides with add_slide, content with the text/shape/table/image tools. The new deck star...
This record as markdown: /tools/a1-x-tech-mcp-google-slides/create-presentation.md
What create_presentation does on Mcp Google Slides
AI agents use create_presentation to create or update resources in Mcp Google Slides, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Slides environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | The presentation title (also the Drive file name). |
Parameters from the server's own tool schema.
Why create_presentation is rated Medium
Creates a new reversible resource in user's Drive; no financial impact or data destruction.
From the tool's definition Creates a new Google Slides presentation, returns presentationId, belongs to authorized user's Drive.
Attacks that exploit this kind of access
The rule that runs create_presentation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Slides, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_presentation, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Slides, apply this rule, and every create_presentation call is checked against it from then on.
Questions about create_presentation
Creates a new Google Slides presentation and returns it (presentationId, revisionId, pageSize, the initial title slide with its object ids, layouts and masters). The API honors only the title at creation — add slides with add_slide, content with the text/shape/table/image tools. The new deck starts with one title slide and belongs to the authorized user's Drive. Note: this server cannot delete a presentation; removing the file is a Drive operation outside its scope. It is categorised as a Write tool in the Mcp Google Slides MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_presentation accepts 1 parameter: title. Required: title. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp 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 Mcp 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 Mcp Google Slides MCP server (@a1-x-tech/mcp-google-slides). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Slides, and thousands of servers like it.
This server
Across the catalogue