debug_mode · InSite MCP: Risk & Policy

WHAT IT DOES

What debug_mode does on InSite

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

Toggling debug/logging modes triggers a change in the running browser automation system's operational state, which is an external operation with side effects (altered logging, potential exposure of sensitive data in logs, performance impacts). It doesn't merely read data nor does it delete or write user content, so Execute is the most appropriate category.

From the tool's definition 'Enable or disable comprehensive debugging mode with enhanced logging' — toggles a system-level operational mode affecting logging and debug behavior

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debug_mode Rate-limited

debug_mode 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": {
    "debug_mode": {
      "limits": [
        {
          "counter": "debug_mode_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 debug_mode

What does the debug_mode tool do? +

Enable or disable comprehensive debugging mode with enhanced logging. 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 debug_mode? +

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

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

Can I rate-limit debug_mode? +

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

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

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