files_revoke_public_url

Revoke public/external sharing access for a file.

SERVERSlack SOURCEkarbassi/slack-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/karbassi-slack-mcp/files-revoke-public-url.md

WHAT IT DOES

What files_revoke_public_url does on Slack

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

RISK

Why files_revoke_public_url is rated Critical

Revoking public URL access is an irreversible action that removes external sharing capabilities for a file. Once revoked, any external links to the file will stop working, and previously shared access cannot be automatically restored. This constitutes a destructive operation with potentially high impact if an AI agent misuses it on files that were intentionally shared publicly.

From the tool's definition Revoke public/external sharing access for a file

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs files_revoke_public_url safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For files_revoke_public_url, this is the rule to start with:

files_revoke_public_url Hidden

files_revoke_public_url is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every files_revoke_public_url call is checked against it from then on.

FAQ

Questions about files_revoke_public_url

What does the files_revoke_public_url tool do? +

Revoke public/external sharing access for a file. It is categorised as a Destructive tool in the Slack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on files_revoke_public_url? +

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

What risk level is files_revoke_public_url? +

files_revoke_public_url 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 files_revoke_public_url? +

Yes. Add a rate_limit block to the files_revoke_public_url 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 files_revoke_public_url completely? +

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

files_revoke_public_url is provided by the Slack MCP server (karbassi/slack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Slack, and thousands of servers like it.

This server

All 233 Slack tools → Critical-risk tools on this server →

Across the catalogue

web3_revoke_key on 0xarchive →disinfect_files on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →