calls_update

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/calls-update.md

WHAT IT DOES

What calls_update does on Slack

AI agents use calls_update 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 calls_update is rated Medium

Based on the name 'calls_update' and the fact that this server grants comprehensive Slack access with 220 tools, this tool most likely modifies call-related data (settings, metadata, status, etc.) in Slack. This is Write-category behavior (reversible modification).

From the tool's definition Tool name 'calls_update' with no description; context shows this is part of slack-mcp providing 'full access to Slack' including messages, channels, files, etc. The update verb indicates modification of call records/settings.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

calls_update Rate-limited

calls_update 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": {
    "calls_update": {
      "limits": [
        {
          "counter": "calls_update_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 calls_update call is checked against it from then on.

FAQ

Questions about calls_update

What does the calls_update tool do? +

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

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

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

Can I rate-limit calls_update? +

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

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

calls_update 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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