run-health-check-group · Mcp Dev MCP: Risk & Policy

WHAT IT DOES

What run-health-check-group does on Mcp Dev

AI agents invoke run-health-check-group to trigger actions in Mcp Dev. 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 run-health-check-group needs a policy

This tool executes system diagnostic operations, making it an Execute category tool rather than Read because it runs active processes with potential side effects (performance impact). The severity is high because unconstrained execution of diagnostics could consume resources, affect availability, or reveal sensitive system information.

From the tool's definition Tool name 'run-health-check-group' explicitly states it 'Executes health checks' and the description warns it 'will run system diagnostics' that 'could temporarily affect system performance.' This is a triggered operation with external effects on the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run-health-check-group Rate-limited

run-health-check-group 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": {
    "run-health-check-group": {
      "limits": [
        {
          "counter": "run-health-check-group_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 Mcp Dev, so you can run agents against it safely.

FAQ

Questions about run-health-check-group

What does the run-health-check-group tool do? +

Executes health checks for a specific group. WARNING: This will run system diagnostics which may take time and could temporarily affect system performance. It is categorised as a Execute tool in the Mcp Dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run-health-check-group? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for run-health-check-group: 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 Mcp Dev. Nothing to install.

What risk level is run-health-check-group? +

run-health-check-group is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run-health-check-group? +

Yes. Add a rate_limit block to the run-health-check-group 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 run-health-check-group completely? +

Set action: deny in the PolicyLayer policy for run-health-check-group. 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 run-health-check-group? +

run-health-check-group is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.