reload_page · InSite MCP: Risk & Policy

WHAT IT DOES

What reload_page does on InSite

AI agents invoke reload_page to trigger actions in InSite. 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_page needs a policy

Reloading a page is an external browser operation that can cause non-trivial side effects such as re-submitting POST forms, resetting in-progress operations, or re-triggering server-side actions. It falls under Execute as it triggers an external operation whose effects depend on the current page context.

From the tool's definition 'Reload the current page' — triggers a browser navigation action that re-executes all page scripts, re-fires network requests, and may cause side effects depending on the page (e.g., re-submitting forms, re-triggering analytics, resetting state).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reload_page Rate-limited

reload_page 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_page": {
      "limits": [
        {
          "counter": "reload_page_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 InSite, so you can run agents against it safely.

FAQ

Questions about reload_page

What does the reload_page tool do? +

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

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

What risk level is reload_page? +

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

Can I rate-limit reload_page? +

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

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

reload_page is provided by the InSite MCP server (jowharshamshiri/insite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.