Low Risk

slack_users_info

Get information about a specific user

How to control slack_users_info ↓

AI agents call slack_users_info to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

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.

Documented attack patterns abuse exactly the kind of access slack_users_info gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for slack_users_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "slack_users_info": {}
  }
}

slack_users_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the slack_users_info tool do? +

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.

How do I enforce a policy on slack_users_info? +

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.

What risk level is slack_users_info? +

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

Can I rate-limit slack_users_info? +

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.

How do I block slack_users_info completely? +

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.

What MCP server provides slack_users_info? +

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.

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.