create_filter_from_template · Gmail MCP: Risk & Policy

WHAT IT DOES

What create_filter_from_template does on Gmail

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

WHY IT NEEDS A POLICY

Why create_filter_from_template needs a policy

Creating an email filter is a write operation that modifies account settings reversibly. While filters affect email behavior (routing, labeling, deletion), the action itself can be undone by deleting the filter. The severity is high because a misconfigured filter applied by an agent could inadvertently hide, mislabel, or auto-delete important emails, causing significant disruption.

From the tool's definition Tool name includes 'create' and description states 'Creates a filter' — this modifies Gmail account configuration by adding a new filter rule.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_filter_from_template Rate-limited

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

FAQ

Questions about create_filter_from_template

What does the create_filter_from_template tool do? +

Creates a filter using a pre-defined template for common scenarios. It is categorised as a Write tool in the Gmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_filter_from_template? +

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

What risk level is create_filter_from_template? +

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

Can I rate-limit create_filter_from_template? +

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

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

create_filter_from_template is provided by the Gmail MCP server (pouyanafisi/gmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.