Update borders of cells in a Google Sheet
AI agents use sheets_update_borders to create or update resources in Mcp Gsheets — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gsheets environment.
Updating borders is a non-destructive modification of spreadsheet cell formatting. It creates or modifies data (cell border properties) but is fully reversible—borders can be removed or changed. This fits the Write category (reversible modification) rather than Read (no changes) or Destructive (permanent loss).
From the tool's definition Tool name 'sheets_update_borders' and description 'Update borders of cells in a Google Sheet' indicate modification of cell formatting properties. This is a reversible change to cell styling/presentation.
Attacks that exploit this kind of access
Update borders of cells in a Google Sheet. It is categorised as a Write tool in the Mcp Gsheets MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gsheets MCP server in PolicyLayer and add a rule for sheets_update_borders: 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 Gsheets. Nothing to install.
sheets_update_borders 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 sheets_update_borders 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 sheets_update_borders. 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.
sheets_update_borders is provided by the Mcp Gsheets MCP server (mcp-gsheets). 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 →