scout_click · Scout MCP: Risk & Policy

WHAT IT DOES

What scout_click does on Scout

AI agents invoke scout_click to trigger actions in Scout. 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 scout_click needs a policy

Clicking a browser element is an Execute-class action because its effects are entirely argument-dependent: a click could submit a payment form, delete content, navigate away, or trigger arbitrary web application logic. The server description confirms it enables AI agents to interact with web pages, amplifying the blast radius.

From the tool's definition 'Click an element by its snapshot ID' — triggers browser click actions that can submit forms, navigate pages, activate UI controls, or trigger any web operation depending on the target element.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scout_click Rate-limited

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

FAQ

Questions about scout_click

What does the scout_click tool do? +

Click an element by its snapshot ID. Returns healer result describing what changed. If stateChange is. It is categorised as a Execute tool in the Scout MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scout_click? +

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

What risk level is scout_click? +

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

Can I rate-limit scout_click? +

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

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

scout_click is provided by the Scout MCP server (lautrek/scout). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.