Update text style (bold, italic, font, color, etc.) for a range of text. Only specified fields are changed.
AI agents use gdoc_update_text_style to create or update resources in Google Docs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Docs environment.
This tool creates reversible changes to document content (formatting/styling). It does not retrieve data (Read), execute arbitrary code (Execute), irreversibly delete data (Destructive), or move money (Financial). The primary risk is unintended modification of document appearance and structure.
From the tool's definition Tool description states 'Update text style (bold, italic, font, color, etc.) for a range of text' — modifies document formatting and styling without deleting or executing code.
Attacks that exploit this kind of access
Update text style (bold, italic, font, color, etc.) for a range of text. Only specified fields are changed. It is categorised as a Write tool in the Google Docs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Docs MCP server in PolicyLayer and add a rule for gdoc_update_text_style: 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 Docs. Nothing to install.
gdoc_update_text_style 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 gdoc_update_text_style 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 gdoc_update_text_style. 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.
gdoc_update_text_style is provided by the Google Docs MCP server (node2flow-th/google-docs-mcp-community). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →