invite_user_to_channel
Add one or more users to a Slack channel. Resolve emails to IDs first via lookup_user_by_email, then pass comma-separated IDs (max 1000). force=true (default) continues inviting valid users when some IDs are invalid.
This record as markdown: /tools/freshdesk/invite-user-to-channel.md
What invite_user_to_channel does on Freshdesk
AI agents use invite_user_to_channel to create or update resources in Freshdesk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshdesk environment.
Why invite_user_to_channel is rated Medium
This tool creates or modifies channel membership by adding users, which is a reversible state change (users can be removed later). It does not delete data, execute arbitrary code, or move money. The severity is medium because misuse could spam users with unwanted channel additions or grant unintended access to channels, but the effects are recoverable.
From the tool's definition Tool invites/adds users to a Slack channel—a reversible modification operation. Description states 'Add one or more users to a Slack channel' and accepts user IDs to perform the invitation.
Attacks that exploit this kind of access
The rule that runs invite_user_to_channel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For invite_user_to_channel, this is the rule to start with:
invite_user_to_channel 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 Freshdesk, apply this rule, and every invite_user_to_channel call is checked against it from then on.
Questions about invite_user_to_channel
Add one or more users to a Slack channel. Resolve emails to IDs first via lookup_user_by_email, then pass comma-separated IDs (max 1000). force=true (default) continues inviting valid users when some IDs are invalid. It is categorised as a Write tool in the Freshdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freshdesk MCP server in PolicyLayer and add a rule for invite_user_to_channel: 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 Freshdesk. Nothing to install.
invite_user_to_channel 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 invite_user_to_channel 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 invite_user_to_channel. 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.
invite_user_to_channel is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue