insert_date · Google MCP: Risk & Policy

WHAT IT DOES

What insert_date does on Google

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

This tool creates/modifies content in a Google Doc by inserting a date element. It is reversible (the date can be deleted or replaced), so it falls under Write rather than Destructive or Execute. The blast radius is minimal — inserting a date chip is a low-risk document edit with no ability to delete data, execute code, or cause financial harm.

From the tool's definition Tool name is 'insert_date' and description states 'Insert a date chip into a Google Doc.' The word 'Insert' indicates creation/modification of document content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insert_date Rate-limited

insert_date 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_date": {
      "limits": [
        {
          "counter": "insert_date_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 insert_date

What does the insert_date tool do? +

Insert a date chip into a Google Doc. 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 insert_date? +

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

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

Can I rate-limit insert_date? +

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

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

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