system-diagnostics | PolicyLayer

WHAT IT DOES

What system-diagnostics does on IMCP - Insecure Model Context Protocol

AI agents invoke system-diagnostics to trigger actions in IMCP - Insecure Model Context Protocol. 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 system-diagnostics needs a policy

This tool executes system operations rather than simply reading static data. System diagnostics can enumerate system configuration, running processes, installed software, network status, and other sensitive operational details.

From the tool's definition 'Run system diagnostics and health checks' - the verb 'Run' indicates active execution of system-level operations that can inspect, monitor, or trigger diagnostic processes whose effects depend on arguments and system state.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

system-diagnostics Rate-limited

system-diagnostics 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": {
    "system-diagnostics": {
      "limits": [
        {
          "counter": "system-diagnostics_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 IMCP - Insecure Model Context Protocol, so you can run agents against it safely.

FAQ

Questions about system-diagnostics

What does the system-diagnostics tool do? +

Run system diagnostics and health checks. It is categorised as a Execute tool in the IMCP - Insecure Model Context Protocol MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on system-diagnostics? +

Register the IMCP - Insecure Model Context Protocol MCP server in PolicyLayer and add a rule for system-diagnostics: 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 IMCP - Insecure Model Context Protocol. Nothing to install.

What risk level is system-diagnostics? +

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

Can I rate-limit system-diagnostics? +

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

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

system-diagnostics is provided by the IMCP - Insecure Model Context Protocol MCP server (nav33n25/imcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.