debug-log · Defcon MCP: Risk & Policy

WHAT IT DOES

What debug-log does on Defcon

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

WHY IT NEEDS A POLICY

Why debug-log needs a policy

This tool creates or modifies log data in a reversible manner. Logging is a non-destructive write operation that does not alter game state, trigger gameplay mechanics, or cause irreversible changes.

From the tool's definition Tool name 'debug-log' and description 'Logs a message to the game' indicate writing data (log messages) to the game's logging system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debug-log Rate-limited

debug-log 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-log": {
      "limits": [
        {
          "counter": "debug-log_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Defcon, so you can run agents against it safely.

FAQ

Questions about debug-log

What does the debug-log tool do? +

Logs a message to the game. It is categorised as a Write tool in the Defcon 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-log? +

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

What risk level is debug-log? +

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

Can I rate-limit debug-log? +

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

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

debug-log is provided by the Defcon MCP server (jorisvddonk/defcon-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.