setElementText
Replace the entire text of one shape/text box by objectId (element-scoped delete+insert in one atomic call). Unlike replaceAllTextInSlides, this cannot hit other slides, masters, or layouts, and does not depend on matching existing text. Pass empty text to clear the element.
This record as markdown: /tools/ark7-google-drive-mcp/setelementtext.md
What setElementText does on Google Drive
AI agents use setElementText to create or update resources in Google Drive, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | New text content (empty string clears the element) |
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 |
objectId | string | Yes | Object ID of the shape or text box (from getSlideElementInfo / getGoogleSlidesContent) |
presentationId | string | Yes | Presentation ID |
Parameters from the server's own tool schema.
Why setElementText is rated Medium
Modifies presentation content reversibly within a single element scope without deletion of underlying objects.
From the tool's definition Replace entire text of shape/text box, atomic call, clear element
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs setElementText 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 setElementText, this is the rule to start with:
setElementText 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 Google Drive, apply this rule, and every setElementText call is checked against it from then on.
Questions about setElementText
Replace the entire text of one shape/text box by objectId (element-scoped delete+insert in one atomic call). Unlike replaceAllTextInSlides, this cannot hit other slides, masters, or layouts, and does not depend on matching existing text. Pass empty text to clear the element. It is categorised as a Write tool in the Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
setElementText accepts 4 parameters: text, account, objectId, presentationId. Required: text, objectId, 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 setElementText: 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.
setElementText 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 setElementText 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 setElementText. 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.
setElementText 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