This record as markdown: /tools/karbassi-slack-mcp/bots-info.md
What bots_info does on Slack
AI agents call bots_info 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 bots_info is rated Low
This tool retrieves metadata about bot users in Slack, which is a read-only query operation. It has no side effects, does not modify data, execute code, delete resources, or involve financial transactions. The blast radius of misuse is minimal—an attacker could enumerate bot users or gather reconnaissance information, but cannot alter systems or data.
From the tool's definition Tool name 'bots_info' and description 'Get info for a bot user' indicate a retrieval operation that queries information about bot users without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs bots_info 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 bots_info, this is the rule to start with:
bots_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 Slack, apply this rule, and every bots_info call is checked against it from then on.
Questions about bots_info
Get info for a bot user. 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 bots_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 Slack. Nothing to install.
bots_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 bots_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 bots_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.
bots_info 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