adaptercloud_files_revoke
Revoke an existing file share by ID (mirrors SDK files.shareApi.revoke). Returns the updated share record with revokedAt/revokedBy set.
This record as markdown: /tools/burdenoff-adaptercloud-mcp/adaptercloud-files-revoke.md
What adaptercloud_files_revoke does on Adaptercloud
AI agents call adaptercloud_files_revoke to permanently remove resources in Adaptercloud, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Share ID to revoke |
Parameters from the server's own tool schema.
Why adaptercloud_files_revoke is rated Critical
An AI agent that decides to call adaptercloud_files_revoke doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Adaptercloud is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs adaptercloud_files_revoke safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adaptercloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adaptercloud_files_revoke, this is the rule to start with:
adaptercloud_files_revoke 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 Adaptercloud, apply this rule, and every adaptercloud_files_revoke call is checked against it from then on.
Questions about adaptercloud_files_revoke
Revoke an existing file share by ID (mirrors SDK files.shareApi.revoke). Returns the updated share record with revokedAt/revokedBy set. It is categorised as a Destructive tool in the Adaptercloud MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
adaptercloud_files_revoke accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Adaptercloud MCP server in PolicyLayer and add a rule for adaptercloud_files_revoke: 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 Adaptercloud. Nothing to install.
adaptercloud_files_revoke 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 adaptercloud_files_revoke 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 adaptercloud_files_revoke. 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.
adaptercloud_files_revoke is provided by the Adaptercloud MCP server (@burdenoff/adaptercloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adaptercloud, and thousands of servers like it.
Across the catalogue