users_custom_status_list

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/users-custom-status-list.md

WHAT IT DOES

What users_custom_status_list does on Slack

AI agents call users_custom_status_list 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 users_custom_status_list is rated Low

This tool retrieves user custom status data from Slack, which is a read-only operation with no side effects. Despite the empty description, the naming convention strongly suggests data retrieval. The risk is low because custom status information is generally non-sensitive metadata in workspace contexts.

From the tool's definition Tool name 'users_custom_status_list' indicates it lists/retrieves user custom status information. The 'list' suffix is characteristic of Read operations that query data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

users_custom_status_list Allowed

users_custom_status_list 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": {
    "users_custom_status_list": {}
  }
}

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 users_custom_status_list call is checked against it from then on.

FAQ

Questions about users_custom_status_list

What does the users_custom_status_list tool do? +

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

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

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

Can I rate-limit users_custom_status_list? +

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

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

users_custom_status_list 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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