saved_get

A read tool on the Slack MCP server.

SERVERSlack SOURCEkarbassi/slack-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What saved_get does on Slack

AI agents call saved_get to retrieve information from Slack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why saved_get is rated Low

The 'get' suffix strongly suggests a read operation that retrieves data without modification. The empty description reduces confidence slightly, but the naming convention and the server's stated focus on providing access to Slack data (messages, channels, files, etc.) supports classification as Read. No side effects, destructive actions, or financial impact are implied.

From the tool's definition Tool name 'saved_get' indicates a retrieval operation ('get') on saved items, likely messages, files, or other Slack content marked as saved by the user.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

saved_get Allowed

saved_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "saved_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about saved_get

What does the saved_get tool do? +

saved_get is a read tool on the Slack MCP server. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on saved_get? +

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

saved_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit saved_get? +

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

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

saved_get 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →