High Risk →

gmail_users_stop

Stop push notifications for the mailbox

Disables mailbox notifications

Part of the Google Workspace Gmail (gws CLI) MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@gws mcp -s gmail Execute Risk 3/5

AI agents invoke gmail_users_stop to trigger processes or run actions in Google Workspace Gmail (gws CLI). Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

gmail_users_stop can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

google-workspace-gmail.yaml
tools:
  gmail_users_stop:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Google Workspace Gmail (gws CLI) policy for all 79 tools.

Tool Name gmail_users_stop
Category Execute
Risk Level High

View all 79 tools →

Agents calling execute-class tools like gmail_users_stop have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

gmail_users_stop is one of the high-risk operations in Google Workspace Gmail (gws CLI). For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the gmail_users_stop tool do? +

Stop push notifications for the mailbox. It is categorised as a Execute tool in the Google Workspace Gmail (gws CLI) MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on gmail_users_stop? +

Add a rule in your Intercept YAML policy under the tools section for gmail_users_stop. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Workspace Gmail (gws CLI) MCP server.

What risk level is gmail_users_stop? +

gmail_users_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gmail_users_stop? +

Yes. Add a rate_limit block to the gmail_users_stop rule in your Intercept 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 gmail_users_stop completely? +

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

gmail_users_stop is provided by the Google Workspace Gmail (gws CLI) MCP server (@gws mcp -s gmail). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Google Workspace Gmail (gws CLI)

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.