debug_validation_report · Pen MCP: Risk & Policy

WHAT IT DOES

What debug_validation_report does on Pen

AI agents invoke debug_validation_report to trigger actions in Pen. 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_validation_report needs a policy

This tool executes validation logic ('run') on the current document. While the detectors are described as 'pure-function' (suggesting no side effects), the action is execution of code/logic rather than simple data retrieval.

From the tool's definition Tool name 'debug_validation_report' and description 'Run pure-function design quality detectors on the current document' indicate execution of analysis/detection functions against document content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debug_validation_report Rate-limited

debug_validation_report 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_validation_report": {
      "limits": [
        {
          "counter": "debug_validation_report_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 Pen, so you can run agents against it safely.

FAQ

Questions about debug_validation_report

What does the debug_validation_report tool do? +

Run pure-function design quality detectors on the current document. It is categorised as a Execute tool in the Pen 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_validation_report? +

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

What risk level is debug_validation_report? +

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

Can I rate-limit debug_validation_report? +

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

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

debug_validation_report is provided by the Pen MCP server (@zseven-w/pen-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.