This record as markdown: /tools/karbassi-slack-mcp/conversations-info.md
What conversations_info does on Slack
AI agents call conversations_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 conversations_info is rated Low
This is a straightforward Read operation—it retrieves conversation metadata from Slack without creating, modifying, or deleting data. Severity is medium rather than low because conversation metadata (names, descriptions, membership, topics, pins) can reveal sensitive organizational information and thus has moderate blast radius if exposed to unauthorized agents; however, it causes no direct harm or side effects.
From the tool's definition Tool name 'conversations_info' and description 'Retrieve information about a conversation' indicate a query/retrieval operation with no data modification.
Attacks that exploit this kind of access
The rule that runs conversations_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 conversations_info, this is the rule to start with:
conversations_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 conversations_info call is checked against it from then on.
Questions about conversations_info
Retrieve information about a conversation. 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 conversations_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.
conversations_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 conversations_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 conversations_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.
conversations_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