// MCP TOOL REFERENCE

revoke_file_share

ServerDock
CategoryDestructive
Parameters3 (3 required)

WHAT IT DOES

What revoke_file_share does on Dock

AI agents call revoke_file_share to permanently remove resources in Dock — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`slug`	string	Yes	The workspace slug.
`file_id`	string	Yes	The file cuid.
`token_id`	string	Yes	The share token id returned by `share_file` (NOT the `url` token). Same id appears in the `list_file_shares` response.

Parameters from the server's own tool schema.

THE RISK

Critical Risk

Why revoke_file_share needs a policy

Revoking a share token immediately breaks public access to the shared file URL. While described as a 'soft' revoke and is idempotent, the action is not trivially reversible from the perspective of anyone who had the link — access is cut off immediately.

From the tool's definition 'Soft-revoke a share token... The public /share/files/<token> URL stops resolving immediately'

Documented attack patterns abuse exactly the kind of access revoke_file_share gives an agent:

POLICY

How to control revoke_file_share

PolicyLayer is an MCP gateway — it sits between your AI agents and Dock, and nothing reaches the server without passing your rules. This is the rule we recommend for revoke_file_share:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "revoke_file_share"
  ]
}

revoke_file_share disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Dock — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Dock tools

Financial downgrade_plan Schedule a downgrade to Free at the end of the current billing period. The org keeps its c Financial upgrade_plan Move the caller's org to Pro ($19/mo flat, 10 agents, 20 members, 200 workspaces, 5k rows Destructive delete_file Soft-delete a file by id. Moves to a 30-day trash window before the cleanup cron hard-dele Destructive delete_row Permanently delete a row from a workspace. This action cannot be undone. Destructive delete_surface Archive a surface (soft-delete). Rows + doc body are preserved for restore. Idempotent: ca Destructive delete_webhook Permanently delete a webhook endpoint. The URL stops receiving events immediately and the Destructive delete_workspace Archive a workspace. Soft-delete: rows, doc body, and activity history are preserved, and Destructive remove_workspace_member Remove a workspace member. Editor role required; owner-tier removals require an owner call

All 64 Dock tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Dock → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about revoke_file_share

What does the revoke_file_share tool do? +

Soft-revoke a share token minted via share_file. The public /share/files/<token> URL stops resolving immediately. Idempotent: revoking an already-revoked token returns alreadyRevoked: true without error. Editor role required. Gated behind FILES_SURFACE_ENABLED + per-user allowlist. It is categorised as a Destructive tool in the Dock MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does revoke_file_share accept? +

revoke_file_share accepts 3 parameters: slug, file_id, token_id. Required: slug, file_id, token_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on revoke_file_share? +

Register the Dock MCP server in PolicyLayer and add a rule for revoke_file_share: 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 Dock. Nothing to install.

What risk level is revoke_file_share? +

revoke_file_share is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit revoke_file_share? +

Yes. Add a rate_limit block to the revoke_file_share 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.

How do I block revoke_file_share completely? +

Set action: deny in the PolicyLayer policy for revoke_file_share. 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.

What MCP server provides revoke_file_share? +

revoke_file_share is provided by the Dock MCP server (https://trydock.ai/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.