modify_table · Google MCP: Risk & Policy

WHAT IT DOES

What modify_table does on Google

AI agents use modify_table to create or update resources in Google — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google environment.

WHY IT NEEDS A POLICY

Why modify_table needs a policy

modify_table performs structural modifications to table elements (rows/columns) in Google Docs. Insert operations are clearly Write. Delete operations on table rows/columns are technically reversible (undo available, and rows can be re-added), unlike permanent document/file deletion. The tool requires precise index parameters, suggesting controlled edits rather than bulk destructive operations.

From the tool's definition Tool description states 'Insert or delete rows/columns in a Google Doc table' — the insert operation is reversible write action; while delete suggests destructive potential, the context (structured table operations with required index parameters) indicates…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

modify_table Rate-limited

modify_table 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "modify_table": {
      "limits": [
        {
          "counter": "modify_table_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google, so you can run agents against it safely.

FAQ

Questions about modify_table

What does the modify_table tool do? +

Insert or delete rows/columns in a Google Doc table. Requires the table start index (from read_doc structure). It is categorised as a Write tool in the Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on modify_table? +

Register the Google MCP server in PolicyLayer and add a rule for modify_table: 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. Nothing to install.

What risk level is modify_table? +

modify_table is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit modify_table? +

Yes. Add a rate_limit block to the modify_table 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.

How do I block modify_table completely? +

Set action: deny in the PolicyLayer policy for modify_table. 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.

What MCP server provides modify_table? +

modify_table is provided by the Google MCP server (ztgluis/google-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.