resources_detach_storage
Run resources.detach-storage through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-detach-storage.md
What resources_detach_storage does on Appaloft
AI agents call resources_detach_storage 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 |
|---|---|---|---|
resourceId | string | Yes | |
attachmentId | string | Yes |
Parameters from the server's own tool schema.
Why resources_detach_storage is rated Critical
Detaching storage from an application resource removes the association between the resource and its storage backend. This operation is likely irreversible in the sense that data on the storage may become inaccessible or orphaned, and the application may lose its persistent data.
From the tool's definition 'detach-storage' — detaching storage from a resource is typically irreversible or disruptive; data may become inaccessible or lost
Attacks that exploit this kind of access
The rule that runs resources_detach_storage 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_detach_storage, this is the rule to start with:
resources_detach_storage 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_detach_storage call is checked against it from then on.
Questions about resources_detach_storage
Run resources.detach-storage 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_detach_storage accepts 2 parameters: resourceId, attachmentId. Required: resourceId, attachmentId. 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_detach_storage: 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_detach_storage 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_detach_storage 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_detach_storage. 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_detach_storage 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