AI agents call conversations_list_connect_invites to retrieve information from Slack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates shared channel invitations, which is a read-only query operation. It has no side effects, does not modify or delete data, and poses minimal security risk. The blast radius of misuse is limited to information disclosure of invitation metadata.
From the tool's definition Tool name 'conversations_list_connect_invites' and description 'List shared channel invites' both indicate a retrieval/query operation with no modification or deletion of data.
Attacks that exploit this kind of access
List shared channel invites. 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_list_connect_invites: 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_list_connect_invites 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_list_connect_invites 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_list_connect_invites. 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_list_connect_invites 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →