getGoogleSlidesContent
Get content of Google Slides with element IDs for formatting
This record as markdown: /tools/ark7-google-drive-mcp/getgoogleslidescontent.md
What getGoogleSlidesContent does on Google Drive
AI agents call getGoogleSlidesContent to retrieve information from Google Drive without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
slideIndex | number | — | Specific slide index (optional) |
presentationId | string | Yes | Presentation ID |
Parameters from the server's own tool schema.
Why getGoogleSlidesContent is rated Low
This tool retrieves and queries the content and structure of Google Slides presentations without modifying, deleting, or executing any operations. It has no side effects and presents minimal risk even if misused by an AI agent, as it only exposes existing data. Confidence is high because the 'get' verb and description clearly indicate a read-only operation.
From the tool's definition Tool name 'getGoogleSlidesContent' and description 'Get content of Google Slides' indicate retrieval-only operation. The phrase 'for formatting' suggests it returns structural/formatting metadata, which is still a read operation.
Attacks that exploit this kind of access
The rule that runs getGoogleSlidesContent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getGoogleSlidesContent, this is the rule to start with:
getGoogleSlidesContent is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Drive, apply this rule, and every getGoogleSlidesContent call is checked against it from then on.
Questions about getGoogleSlidesContent
Get content of Google Slides with element IDs for formatting. It is categorised as a Read tool in the Google Drive MCP Server, which means it retrieves data without modifying state.
getGoogleSlidesContent accepts 3 parameters: account, slideIndex, presentationId. Required: presentationId. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for getGoogleSlidesContent: 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 Drive. Nothing to install.
getGoogleSlidesContent is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getGoogleSlidesContent 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 getGoogleSlidesContent. 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.
getGoogleSlidesContent is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue