execute-health-check-action · Mcp Dev MCP: Risk & Policy

WHAT IT DOES

What execute-health-check-action does on Mcp Dev

AI agents invoke execute-health-check-action 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 execute-health-check-action needs a policy

While the tool could theoretically be Destructive if it performs irreversible deletions, the description emphasizes 'remedial actions' and 'health checks' which suggest corrective rather than destructive intent. However, the explicit warning about modifying system configuration, files, and database content, combined with the execution model, places this in Execute category.

From the tool's definition Tool description explicitly states 'Executes remedial actions for health issues' and warns that it 'may modify system configuration, files, or database content.' The verb 'Executes' combined with the scope of potential side effects (configuration, files,…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute-health-check-action Rate-limited

execute-health-check-action 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": {
    "execute-health-check-action": {
      "limits": [
        {
          "counter": "execute-health-check-action_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 execute-health-check-action

What does the execute-health-check-action tool do? +

Executes remedial actions for health issues. WARNING: This performs system remedial actions that may modify system configuration, files, or database content. Use with caution. 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 execute-health-check-action? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for execute-health-check-action: 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 execute-health-check-action? +

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

Can I rate-limit execute-health-check-action? +

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

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

execute-health-check-action 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.