saved_delete

A destructive tool on the Slack MCP server.

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/saved-delete.md

WHAT IT DOES

What saved_delete does on Slack

AI agents call saved_delete 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 saved_delete is rated Critical

The tool name strongly suggests permanent deletion of saved Slack content. Although the description is empty, the semantic meaning of 'delete' in a data context indicates an irreversible destructive action. Given the server's scope (Slack workspace access with 220 tools), misuse could result in loss of important saved messages or organizational knowledge.

From the tool's definition Tool name 'saved_delete' indicates deletion of saved items in Slack. The 'delete' verb combined with 'saved' (referring to saved messages, searches, or bookmarks) suggests irreversible removal of user data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs saved_delete 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 saved_delete, this is the rule to start with:

saved_delete Hidden

saved_delete 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": [
    "saved_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about saved_delete

What does the saved_delete tool do? +

saved_delete is a destructive tool on the Slack MCP server. 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 saved_delete? +

Register the Slack MCP server in PolicyLayer and add a rule for saved_delete: 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 saved_delete? +

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

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

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

saved_delete 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

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →