insert_table · Google Connections MCP: Risk & Policy

WHAT IT DOES

What insert_table does on Google Connections

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

WHY IT NEEDS A POLICY

Why insert_table needs a policy

The tool creates new content (a table) within a Google Doc, which is a Write category action. Severity is medium because unauthorized table insertion could deface or corrupt documents and require manual cleanup, but the operation is reversible (tables can be deleted). Confidence is high given the clear descriptive language, though the lack of parameter details prevents absolute certainty about scope constraints.

From the tool's definition Tool name 'insert_table' and description 'Insert a table into a Google Doc' indicate creating/modifying document content. This is a reversible write operation on Google Docs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insert_table Rate-limited

insert_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": {
    "insert_table": {
      "limits": [
        {
          "counter": "insert_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 Connections, so you can run agents against it safely.

FAQ

Questions about insert_table

What does the insert_table tool do? +

Insert a table into a Google Doc. It is categorised as a Write tool in the Google Connections MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on insert_table? +

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

What risk level is insert_table? +

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

Can I rate-limit insert_table? +

Yes. Add a rate_limit block to the insert_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 insert_table completely? +

Set action: deny in the PolicyLayer policy for insert_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 insert_table? +

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