This record as markdown: /tools/karbassi-slack-mcp/users-get-presence.md
What users_get_presence does on Slack
AI agents call users_get_presence 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.
Why users_get_presence is rated Low
This tool retrieves presence status information about users (online, away, etc.). It is a read-only query that does not modify data, execute commands, or trigger external operations. The blast radius of misuse is minimal—an attacker could learn when users are active, but cannot access sensitive content, modify data, delete information, or move money. Low severity reflects the informational nature of the data exposed.
From the tool's definition Tool name 'users_get_presence' and description 'Get user presence information' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs users_get_presence 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_get_presence, this is the rule to start with:
users_get_presence is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every users_get_presence call is checked against it from then on.
Questions about users_get_presence
Get user presence information. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP server in PolicyLayer and add a rule for users_get_presence: 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.
users_get_presence is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the users_get_presence 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.
Set action: deny in the PolicyLayer policy for users_get_presence. 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.
users_get_presence 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.
More on Slack, and thousands of servers like it.
This server
Across the catalogue