conversations_invite_shared
A write tool on the Slack MCP server.
This record as markdown: /tools/karbassi-slack-mcp/conversations-invite-shared.md
What conversations_invite_shared does on Slack
AI agents use conversations_invite_shared to create or update resources in Slack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack environment.
Why conversations_invite_shared is rated Medium
The 'invite' action creates or modifies membership relationships within Slack conversations, which is a reversible write operation. While it doesn't delete data, it does alter permissions and access control. The high severity reflects that an AI agent could be tricked into inviting unauthorized users to sensitive channels or invite spam, affecting organizational security and data access boundaries.
From the tool's definition Tool name 'conversations_invite_shared' indicates inviting users to a shared conversation/channel. Based on sibling tools in the slack-mcp server like 'conversations_*' patterns and the invite action, this modifies channel membership state.
Attacks that exploit this kind of access
The rule that runs conversations_invite_shared 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_invite_shared, this is the rule to start with:
conversations_invite_shared stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_invite_shared call is checked against it from then on.
Questions about conversations_invite_shared
conversations_invite_shared is a write tool on the Slack MCP server. It is categorised as a Write tool in the Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slack MCP server in PolicyLayer and add a rule for conversations_invite_shared: 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_invite_shared is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the conversations_invite_shared 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_invite_shared. 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_invite_shared 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