set_user_status · Slack MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_user_status does on Slack MCP Server

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

WHY IT NEEDS A POLICY

Why set_user_status needs a policy

This tool modifies user status/presence information, which is reversible metadata changes. It does not delete data (not Destructive), execute code or trigger external operations with unknown side effects (not Execute), move money (not Financial), or merely read data (not Read). The blast radius is limited to presence visibility and does not affect critical workspace operations, user access, or financial systems.

From the tool's definition Tool name 'set_user_status' and description 'Definir status do usuário (presença)' [Set user status (presence)] indicate modification of user presence/status metadata in Slack.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_user_status Rate-limited

set_user_status 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": {
    "set_user_status": {
      "limits": [
        {
          "counter": "set_user_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Slack MCP Server, so you can run agents against it safely.

FAQ

Questions about set_user_status

What does the set_user_status tool do? +

Definir status do usuário (presença). It is categorised as a Write tool in the Slack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_user_status? +

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

What risk level is set_user_status? +

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

Can I rate-limit set_user_status? +

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

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

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