post_slack_message
Post a message to a Slack channel as yourself. DM SAFETY: For direct messages (D... channels), this tool verifies the recipient identity before sending. Always provide intended_recipient (User ID) for DMs to enable mismatch detection. The message is NOT sent if intended_recipient does not match t...
This record as markdown: /tools/freshdesk/post-slack-message.md
What post_slack_message does on Freshdesk
AI agents use post_slack_message 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 post_slack_message is rated Medium
This tool creates new data (Slack messages) in a reversible manner. The action is Write rather than Execute because it does not run code or trigger complex external operations—it simply posts text to a channel. While messages are editable and can be deleted, the primary effect is creation/modification of communication data.
From the tool's definition Post a message to a Slack channel as yourself. Messages are editable in Slack. Parameters include channel, text, and intended_recipient.
Attacks that exploit this kind of access
The rule that runs post_slack_message 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 post_slack_message, this is the rule to start with:
post_slack_message 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 post_slack_message call is checked against it from then on.
Questions about post_slack_message
Post a message to a Slack channel as yourself. DM SAFETY: For direct messages (D... channels), this tool verifies the recipient identity before sending. Always provide intended_recipient (User ID) for DMs to enable mismatch detection. The message is NOT sent if intended_recipient does not match the actual DM recipient. PARAMETERS: channel, text, intended_recipient. Do not use channel_id or message — these are not the parameter names. Posted as the user — messages are editable in Slack. 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 post_slack_message: 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.
post_slack_message 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 post_slack_message 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 post_slack_message. 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.
post_slack_message 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