resources_reset_health
Run resources.reset-health through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-reset-health.md
What resources_reset_health does on Appaloft
AI agents invoke resources_reset_health to trigger actions in Appaloft. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
resourceId | string | Yes |
Parameters from the server's own tool schema.
Why resources_reset_health is rated High
The tool executes an operation ('run') against resources to reset their health state. This is an active trigger of an external operation rather than a simple read or write. Resetting health state could affect resource availability and routing decisions across the platform, giving it a high blast radius if misused.
From the tool's definition 'Run resources.reset-health through the Appaloft application operation catalog' — explicitly runs an operation
Attacks that exploit this kind of access
The rule that runs resources_reset_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resources_reset_health, this is the rule to start with:
resources_reset_health 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 Appaloft, apply this rule, and every resources_reset_health call is checked against it from then on.
Questions about resources_reset_health
Run resources.reset-health through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
resources_reset_health accepts 1 parameter: resourceId. Required: resourceId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for resources_reset_health: 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 Appaloft. Nothing to install.
resources_reset_health 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 resources_reset_health 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 resources_reset_health. 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.
resources_reset_health is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue