Enviar mensagem via webhook (para integrações)
AI agents use send_webhook_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.
This tool creates or posts messages to Slack channels through webhook mechanisms, which is a reversible Write operation. While messages can technically be edited or deleted later, the primary action is creating new content.
From the tool's definition Tool name 'send_webhook_message' and description 'Enviar mensagem via webhook (para integrações)' [Send message via webhook (for integrations)] indicate message creation/posting to Slack via webhook integration.
Attacks that exploit this kind of access
Enviar mensagem via webhook (para integrações). 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_webhook_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_webhook_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_webhook_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_webhook_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_webhook_message is provided by the Slack MCP Server MCP server (will2023a/mcp-slack). 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 →