load_page · InSite MCP: Risk & Policy

WHAT IT DOES

What load_page does on InSite

AI agents invoke load_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 load_page needs a policy

This tool triggers a browser navigation action to an arbitrary URL, which is an external operation with side effects depending on the URL argument (e.g., could trigger server-side actions, load malicious content, or initiate downloads). It goes beyond merely reading data — it actively drives a browser to execute a network request and load a page.

From the tool's definition Navigate to a URL and wait for the page to load

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

load_page Rate-limited

load_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": {
    "load_page": {
      "limits": [
        {
          "counter": "load_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 load_page

What does the load_page tool do? +

Navigate to a URL and wait for the page to load. 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 load_page? +

Register the InSite MCP server in PolicyLayer and add a rule for load_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 load_page? +

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

Can I rate-limit load_page? +

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

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

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