High Risk →

diagnose_dev_addon

Run a high-level diagnosis for a local addon project. Validates the manifest, checks the official dev runner health, reads the latest frontend dev snapshot, and summarizes likely causes for hangs/errors.

Accepts file system path (path)

Part of the Addon MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke diagnose_dev_addon to trigger processes or run actions in Addon. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

diagnose_dev_addon can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

addon.yaml
tools:
  diagnose_dev_addon:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Addon policy for all 14 tools.

Tool Name diagnose_dev_addon
Category Execute
MCP Server Addon MCP Server
Risk Level High

View all 14 tools →

Agents calling execute-class tools like diagnose_dev_addon have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

diagnose_dev_addon is one of the high-risk operations in Addon. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the diagnose_dev_addon tool do? +

Run a high-level diagnosis for a local addon project. Validates the manifest, checks the official dev runner health, reads the latest frontend dev snapshot, and summarizes likely causes for hangs/errors.. It is categorised as a Execute tool in the Addon MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on diagnose_dev_addon? +

Add a rule in your Intercept YAML policy under the tools section for diagnose_dev_addon. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Addon MCP server.

What risk level is diagnose_dev_addon? +

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

Can I rate-limit diagnose_dev_addon? +

Yes. Add a rate_limit block to the diagnose_dev_addon rule in your Intercept 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 diagnose_dev_addon completely? +

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

diagnose_dev_addon is provided by the Addon MCP server (@mywallpaper/addon-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Addon

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.