resources_configure_health
Run resources.configure-health through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-configure-health.md
What resources_configure_health does on Appaloft
AI agents invoke resources_configure_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 | |
healthCheck | object | Yes |
Parameters from the server's own tool schema.
Why resources_configure_health is rated High
The tool 'runs' an operation from an application catalog, indicating execution of an action rather than a simple read or write. 'Configure-health' suggests it modifies health check configuration for resources, which could affect service availability and monitoring. The 'run' verb and operation catalog framing place this in Execute.
From the tool's definition "Run resources.configure-health through the Appaloft application operation catalog"
Risk signalsAccepts file system path (healthCheck.http.path) · Accepts URL/endpoint input (healthCheck.http.host) · High parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs resources_configure_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_configure_health, this is the rule to start with:
resources_configure_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_configure_health call is checked against it from then on.
Questions about resources_configure_health
Run resources.configure-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_configure_health accepts 2 parameters: resourceId, healthCheck. Required: resourceId, healthCheck. 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_configure_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_configure_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_configure_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_configure_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_configure_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