This record as markdown: /tools/sagemcp-sagemcp/slack-users-info.md
What slack_users_info does on Sage MCP
AI agents call slack_users_info to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why slack_users_info is rated Low
This tool queries and retrieves user information from Slack without creating, modifying, deleting, or executing any operations. It is a read-only data retrieval function with minimal blast radius if misused by an AI agent—the worst outcome would be unauthorized access to user profile data, which is a confidentiality concern but not destructive or financial.
From the tool's definition Tool name 'slack_users_info' and description 'Get information about a specific user' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs slack_users_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For slack_users_info, this is the rule to start with:
slack_users_info 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 Sage MCP, apply this rule, and every slack_users_info call is checked against it from then on.
Questions about slack_users_info
Get information about a specific user. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for slack_users_info: 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 Sage MCP. Nothing to install.
slack_users_info 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 slack_users_info 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 slack_users_info. 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.
slack_users_info is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue