execute-health-check-action
Executes remedial actions for health issues. WARNING: This performs system remedial actions that may modify system configuration, files, or database content. Use with caution.
This record as markdown: /tools/mcp-dev/execute-health-check-action.md
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 execute-health-check-action is rated High
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
The rule that runs execute-health-check-action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For execute-health-check-action, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every execute-health-check-action call is checked against it from then on.
Questions about execute-health-check-action
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.
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.
execute-health-check-action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on Mcp Dev, and thousands of servers like it.
Across the catalogue