servers_capacity_prune
Run servers.capacity.prune through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/servers-capacity-prune.md
What servers_capacity_prune does on Appaloft
AI agents call servers_capacity_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 | — | |
target | string | — | |
serverId | string | Yes | |
categories | array | — | |
includeOrphanRunning | boolean | — |
Parameters from the server's own tool schema.
Why servers_capacity_prune is rated Critical
'Prune' operations are canonically destructive, removing data or resources that cannot be recovered. Applied to server capacity, this likely deallocates or permanently removes capacity entries. The pattern matches other 'prune' tools on this server (e.g., audit_events_archives_prune). Severity is high because misuse could remove infrastructure capacity affecting live services.
From the tool's definition 'prune' in the tool name and description — 'servers.capacity.prune' — indicates irreversible removal of server capacity resources
Attacks that exploit this kind of access
The rule that runs servers_capacity_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 servers_capacity_prune, this is the rule to start with:
servers_capacity_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 servers_capacity_prune call is checked against it from then on.
Questions about servers_capacity_prune
Run servers.capacity.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.
servers_capacity_prune accepts 6 parameters: before, dryRun, target, serverId, categories, includeOrphanRunning. Required: before, serverId. 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 servers_capacity_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.
servers_capacity_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 servers_capacity_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 servers_capacity_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.
servers_capacity_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