send_notification
Send a notification message to the user via their configured COMMS channels (Telegram, Discord, Slack, Signal).
This record as markdown: /tools/flowdot-llc-mcp-server/send-notification.md
What send_notification does on FlowDot MCP Server
AI agents invoke send_notification to trigger actions in FlowDot MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why send_notification is rated High
This tool triggers an external operation — dispatching a message through third-party communication platforms. It is not a simple write to internal data; it actively sends content to external services (Telegram, Discord, Slack, Signal), making it Execute. Misuse could result in spam, harassment, or social engineering via the user's trusted communication channels, warranting medium severity.
From the tool's definition Send a notification message to the user via their configured COMMS channels (Telegram, Discord, Slack, Signal)
Attacks that exploit this kind of access
The rule that runs send_notification safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_notification, this is the rule to start with:
send_notification stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every send_notification call is checked against it from then on.
Questions about send_notification
Send a notification message to the user via their configured COMMS channels (Telegram, Discord, Slack, Signal). It is categorised as a Execute tool in the FlowDot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for send_notification: 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 FlowDot MCP Server. Nothing to install.
send_notification is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_notification 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. 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 is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
Across the catalogue