AI agents use slack_post_message to create or update resources in MCP-Brave-Search — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Brave-Search environment.
This tool writes data to Slack by creating a new message. While the action is reversible (messages can be edited or deleted), it modifies state in an external system and could be misused to spam, send unauthorized communications, or disrupt workflows. This is categorized as Write rather than Execute because it doesn't run code or trigger arbitrary operations—it specifically creates a message.
From the tool's definition Post a new message to a Slack channel — the tool creates new data (a Slack message) in a channel, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access slack_post_message gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Brave-Search, and nothing reaches the server without passing your rules. This is the rule we recommend for slack_post_message:
{
"version": "1",
"default": "deny",
"tools": {
"slack_post_message": {
"limits": [
{
"counter": "slack_post_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}slack_post_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.
Free to start. No card required.
Post a new message to a Slack channel. It is categorised as a Write tool in the MCP-Brave-Search MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-Brave-Search MCP server in PolicyLayer and add a rule for slack_post_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 MCP-Brave-Search. Nothing to install.
slack_post_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 slack_post_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 slack_post_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.
slack_post_message is provided by the MCP-Brave-Search MCP server (modelcontextprotocol/servers-archived). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Brave-Search, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
59 MCP-Brave-Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.