debug

Set runtime-only overrides (owner-only).

SERVEROpenClaw SOURCEopenclaw

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/openclaw/debug.md

WHAT IT DOES

What debug does on OpenClaw

AI agents use debug to create or update resources in OpenClaw, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenClaw environment.

RISK

Why debug is rated Medium

The tool sets runtime overrides, which is a Write operation modifying system configuration. It does not appear to execute code or irreversibly delete data, though the vague description lowers confidence. The 'owner-only' restriction indicates elevated privilege, raising the severity to medium since misuse could alter system behavior.

From the tool's definition 'Set runtime-only overrides' indicates modifying runtime configuration/state; 'owner-only' suggests privileged access

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs debug safely

PolicyLayer is an MCP gateway: it sits between your AI agents and OpenClaw, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For debug, this is the rule to start with:

debug Rate-limited

debug stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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": {
      "limits": [
        {
          "counter": "debug_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect OpenClaw, apply this rule, and every debug call is checked against it from then on.

FAQ

Questions about debug

What does the debug tool do? +

Set runtime-only overrides (owner-only). It is categorised as a Write tool in the OpenClaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on debug? +

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

What risk level is debug? +

debug is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit debug? +

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

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

debug is provided by the OpenClaw MCP server (openclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on OpenClaw, and thousands of servers like it.

This server

All 129 OpenClaw tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →