handle_csp · InSite MCP: Risk & Policy

WHAT IT DOES

What handle_csp does on InSite

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

This tool modifies how the browser enforces Content Security Policy, which is a security control configuration. Changing CSP handling is an active browser configuration change that affects execution security boundaries. It's not purely destructive (doesn't delete data), but modifying security policy enforcement can enable script injection or bypass protections, making it Execute-level.

From the tool's definition Configure Content Security Policy handling and compliance checking

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

handle_csp Rate-limited

handle_csp 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": {
    "handle_csp": {
      "limits": [
        {
          "counter": "handle_csp_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 handle_csp

What does the handle_csp tool do? +

Configure Content Security Policy handling and compliance checking. 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 handle_csp? +

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

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

Can I rate-limit handle_csp? +

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

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

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