saved_add

A write tool on the Slack MCP server.

SERVERSlack SOURCEkarbassi/slack-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/karbassi-slack-mcp/saved-add.md

WHAT IT DOES

What saved_add does on Slack

AI agents use saved_add to create or update resources in Slack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack environment.

RISK

Why saved_add is rated Medium

The 'add' action is reversible (items can be unsaved), making this a Write rather than Destructive operation. Severity is high because saved items are often used to organize sensitive or important information; misuse could result in unwanted bookmarking of confidential conversations, files, or other Slack objects.

From the tool's definition Tool name 'saved_add' indicates adding to saved items. In the context of a Slack MCP server with 'full access to Slack: messages, channels, files, canvases, lists', this tool creates or modifies saved items (e.g., saving messages, files, or other Slack…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

saved_add Rate-limited

saved_add 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "saved_add": {
      "limits": [
        {
          "counter": "saved_add_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about saved_add

What does the saved_add tool do? +

saved_add is a write tool on the Slack MCP server. It is categorised as a Write tool in the Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on saved_add? +

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

saved_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit saved_add? +

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

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

saved_add 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 →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →