pin_table_header_rows · Google MCP: Risk & Policy

WHAT IT DOES

What pin_table_header_rows does on Google

AI agents use pin_table_header_rows 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 pin_table_header_rows needs a policy

Pinning header rows is a document formatting operation that modifies the table's visual/structural properties in Google Docs. This is a write operation because it alters the document state, but it is reversible (rows can be unpinned) and has no destructive, financial, or code-execution implications. The scope is limited to table formatting within a single document, resulting in low severity.

From the tool's definition Tool description: 'Pin header rows in a Google Doc table.' This modifies document formatting/structure by pinning rows, which is a reversible change to the document's table configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pin_table_header_rows Rate-limited

pin_table_header_rows 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": {
    "pin_table_header_rows": {
      "limits": [
        {
          "counter": "pin_table_header_rows_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 pin_table_header_rows

What does the pin_table_header_rows tool do? +

Pin header rows in a Google Doc table. 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 pin_table_header_rows? +

Register the Google MCP server in PolicyLayer and add a rule for pin_table_header_rows: 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 pin_table_header_rows? +

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

Can I rate-limit pin_table_header_rows? +

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

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

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