reload · Autoconsent MCP: Risk & Policy

WHAT IT DOES

What reload does on Autoconsent MCP

AI agents invoke reload to trigger actions in Autoconsent 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 reload needs a policy

Reloading a page is a browser action with external side effects: it re-issues network requests, re-runs scripts, and may re-trigger consent dialogs or other stateful interactions. This fits Execute as it triggers an external operation whose effects depend on the current browser state.

From the tool's definition 'Reload the current page' — triggers a browser action that re-executes page load, network requests, and any page-level scripts

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reload Rate-limited

reload 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": {
    "reload": {
      "limits": [
        {
          "counter": "reload_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 Autoconsent MCP, so you can run agents against it safely.

FAQ

Questions about reload

What does the reload tool do? +

Reload the current page. It is categorised as a Execute tool in the Autoconsent 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 reload? +

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

What risk level is reload? +

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

Can I rate-limit reload? +

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

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

reload is provided by the Autoconsent MCP server (noisysocks/autoconsent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.