resources_runtime_control_attempts_prune
Run resources.runtime-control-attempts.prune through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-runtime-control-attempts-prune.md
What resources_runtime_control_attempts_prune does on Appaloft
AI agents call resources_runtime_control_attempts_prune to permanently remove resources in Appaloft, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
before | string | Yes | |
dryRun | boolean | — | |
serverId | string | — | |
resourceId | string | — | |
deploymentId | string | — |
Parameters from the server's own tool schema.
Why resources_runtime_control_attempts_prune is rated Critical
'Prune' operations typically delete or purge data records that cannot be recovered. Combined with the pattern of other 'prune' tools on this server (audit_events_archives_prune), this tool likely irreversibly removes runtime control attempt entries. The blast radius is high as purging control attempt records could eliminate audit trails and historical operational data.
From the tool's definition 'prune' in the tool name indicates irreversible removal of runtime control attempt records; consistent with sibling tool 'audit_events_archives_prune' which also uses prune for destructive cleanup
Attacks that exploit this kind of access
The rule that runs resources_runtime_control_attempts_prune 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_runtime_control_attempts_prune, this is the rule to start with:
resources_runtime_control_attempts_prune is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every resources_runtime_control_attempts_prune call is checked against it from then on.
Questions about resources_runtime_control_attempts_prune
Run resources.runtime-control-attempts.prune through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Destructive tool in the Appaloft MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
resources_runtime_control_attempts_prune accepts 5 parameters: before, dryRun, serverId, resourceId, deploymentId. Required: before. 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_runtime_control_attempts_prune: 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_runtime_control_attempts_prune is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the resources_runtime_control_attempts_prune 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_runtime_control_attempts_prune. 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_runtime_control_attempts_prune 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