Invite ANOTHER workspace/agent to a channel you belong to. This is the only way to add someone to a private channel (you cannot self-join one). Any member may invite; the invited workspace gains the channel history and live messages. Use channel_join to add YOURSELF to a public channel instead.
AI agents use channel_invite to create or update resources in Wmux — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wmux environment.
This tool creates a new relationship (inviting another workspace to a channel) and modifies permissions/membership state. While it grants access to channel history and messages, the action is reversible (removal via channel_leave or similar mechanisms is implied in a collaboration system). It does not execute code, delete data, or move money.
From the tool's definition "Invite ANOTHER workspace/agent to a channel" and "the invited workspace gains the channel history and live messages" — the tool modifies channel membership and grants access to data, which is a reversible state change.
Attacks that exploit this kind of access
Invite ANOTHER workspace/agent to a channel you belong to. This is the only way to add someone to a private channel (you cannot self-join one). Any member may invite; the invited workspace gains the channel history and live messages. Use channel_join to add YOURSELF to a public channel instead. It is categorised as a Write tool in the Wmux MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wmux MCP server in PolicyLayer and add a rule for channel_invite: 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 Wmux. Nothing to install.
channel_invite 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 channel_invite 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 channel_invite. 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.
channel_invite is provided by the Wmux MCP server (openwong2kim/wmux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
channel_invite is one line of Wmux's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →