add_columns
AI agents use add_columns 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.
Adding columns to a spreadsheet is a reversible modification operation that creates new data structures within a sheet. This is a Write action rather than Read (no data retrieval), Execute (no external operations triggered), Destructive (reversible), or Financial. Severity is medium because accidental column additions could disrupt spreadsheet structure and downstream workflows, but the action is recoverable.
From the tool's definition Tool name 'add_columns' and server description indicating capability to manage spreadsheet data, alongside sibling tools like 'add_rows' and 'batch_update' which are clearly write operations. Tool description is empty, preventing direct confirmation.
Attacks that exploit this kind of access
add_columns. 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 add_columns: 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.
add_columns 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 add_columns 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 add_columns. 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.
add_columns 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 →