scout_refresh · Scout MCP: Risk & Policy

WHAT IT DOES

What scout_refresh does on Scout

AI agents invoke scout_refresh 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_refresh needs a policy

Refreshing a page triggers a browser action/network request and can cause side effects such as re-submitting forms, re-triggering page scripts, or losing unsaved state. It is not a pure read and goes beyond a simple data write, making Execute the most appropriate category. Misuse could disrupt ongoing workflows or cause unintended form resubmissions.

From the tool's definition Refresh the current page

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scout_refresh Rate-limited

scout_refresh 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_refresh": {
      "limits": [
        {
          "counter": "scout_refresh_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_refresh

What does the scout_refresh tool do? +

Refresh the current page. 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_refresh? +

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

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

Can I rate-limit scout_refresh? +

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

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

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

// THE FULL RECORD

scout_refresh is one line of Scout's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →