send_notification_message
AI agents use send_notification_message to create or update resources in Slack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack MCP Server environment.
Sending messages to Slack is a reversible Write operation—it creates new data (messages) but does not delete, execute arbitrary code, or move funds. Severity is medium because unsupervised message sending could spam channels, impersonate users, or leak sensitive information to unintended audiences.
From the tool's definition Tool name 'send_notification_message' indicates message creation/posting to Slack. Server description confirms 'messaging' as a core capability.
Attacks that exploit this kind of access
send_notification_message. It is categorised as a Write tool in the Slack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slack MCP Server MCP server in PolicyLayer and add a rule for send_notification_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 Slack MCP Server. Nothing to install.
send_notification_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 send_notification_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 send_notification_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.
send_notification_message is provided by the Slack MCP Server MCP server (piekstra/slack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →