stop_web_task · Gemini Web Automation MCP: Risk & Policy

WHAT IT DOES

What stop_web_task does on Gemini Web Automation MCP

AI agents invoke stop_web_task to trigger actions in Gemini Web Automation MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why stop_web_task needs a policy

Stopping a running web task is an Execute action because it triggers external operations that control an active browser session's behavior. While not destructive or financial, it represents code/process execution with side effects dependent on which task is terminated.

From the tool's definition Tool name 'stop_web_task' combined with sibling tools that perform web automation actions (navigate websites, click buttons, fill forms) suggests this tool terminates or interrupts an active web task.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_web_task Rate-limited

stop_web_task stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_web_task": {
      "limits": [
        {
          "counter": "stop_web_task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Gemini Web Automation MCP, so you can run agents against it safely.

FAQ

Questions about stop_web_task

What does the stop_web_task tool do? +

stop_web_task. It is categorised as a Execute tool in the Gemini Web Automation MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_web_task? +

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

What risk level is stop_web_task? +

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

Can I rate-limit stop_web_task? +

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

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

stop_web_task is provided by the Gemini Web Automation MCP server (vincenthopf/computer-use-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.