resources_attach_storage
Run resources.attach-storage through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-attach-storage.md
What resources_attach_storage does on Appaloft
AI agents use resources_attach_storage to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
mountMode | string | — | |
dataFormat | string | — | |
resourceId | string | Yes | |
destinationPath | string | Yes | |
storageVolumeId | string | Yes | |
applicationDataLabel | string | — |
Parameters from the server's own tool schema.
Why resources_attach_storage is rated Medium
Attaching storage to a resource creates or modifies an association between a storage resource and an application. This is a Write operation as it establishes a new binding/configuration, but is likely reversible (can be detached). Severity is high because misconfiguration of storage attachments could expose sensitive data or disrupt application availability.
From the tool's definition 'attach-storage' suggests associating a storage resource with an application, which is a write/configuration operation
Attacks that exploit this kind of access
The rule that runs resources_attach_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_attach_storage, this is the rule to start with:
resources_attach_storage stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_attach_storage call is checked against it from then on.
Questions about resources_attach_storage
Run resources.attach-storage through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
resources_attach_storage accepts 6 parameters: mountMode, dataFormat, resourceId, destinationPath, storageVolumeId, applicationDataLabel. Required: resourceId, destinationPath, storageVolumeId. 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_attach_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_attach_storage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resources_attach_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_attach_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_attach_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.
This server
Across the catalogue