replace_text
AI agents use replace_text to create or update resources in Mcp Google Sheets — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Sheets environment.
Replace_text modifies existing cell content reversibly, fitting Write category. Severity is high because uncontrolled text replacement across a spreadsheet could corrupt significant data, especially if applied to wrong ranges or with incorrect patterns. Not Destructive since replacement is reversible (undo possible). Confidence reduced to 0.85 due to empty tool description, but sibling context is clear.
From the tool's definition Tool name 'replace_text' combined with sibling tools (add_columns, add_rows, batch_update, batch_update_cells, format_range) that modify spreadsheet data.
Attacks that exploit this kind of access
replace_text. It is categorised as a Write tool in the Mcp Google Sheets MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Google Sheets MCP server in PolicyLayer and add a rule for replace_text: 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 Sheets. Nothing to install.
replace_text 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 replace_text 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 replace_text. 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.
replace_text is provided by the Mcp Google Sheets MCP server (yardobr/mcp-google-sheets). 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 →