update-config · Debugger MCP Server MCP: Risk & Policy

WHAT IT DOES

What update-config does on Debugger MCP Server

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

WHY IT NEEDS A POLICY

Why update-config needs a policy

This tool creates or modifies debugger configuration settings reversibly. While configuration changes could affect debugging behavior and potentially expose sensitive information if misconfigured, the action is reversible and does not permanently destroy data or cause irreversible damage. It is less severe than Destructive or Execute (no code execution), but more severe than Read (modifies state).

From the tool's definition Tool name 'update-config' combined with description 'Update debugger configuration rules and settings' indicates modification of configuration data. The verb 'Update' and phrase 'configuration rules and settings' are classic Write indicators.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-config Rate-limited

update-config 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": {
    "update-config": {
      "limits": [
        {
          "counter": "update-config_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 Debugger MCP Server, so you can run agents against it safely.

FAQ

Questions about update-config

What does the update-config tool do? +

Update debugger configuration rules and settings. It is categorised as a Write tool in the Debugger MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update-config? +

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

What risk level is update-config? +

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

Can I rate-limit update-config? +

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

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

update-config is provided by the Debugger MCP Server MCP server (phoenixrr2113/debugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.