Trigger a desktop notification with a custom title, message, and severity level (info, warn, error). This is useful for providing immediate feedback on background task completion or issues.
AI agents invoke alert to trigger actions in Subconductor. 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.
This tool executes an external system operation (triggering desktop notifications) whose effect depends on supplied arguments (title, message, severity). While notifications are not destructive or financial, they do represent execution of code/commands that interact with the operating system.
From the tool's definition Tool description states it 'Trigger[s] a desktop notification' with configurable title, message, and severity level. The verb 'trigger' and the ability to specify custom content indicate execution of a system-level notification operation.
Attacks that exploit this kind of access
Trigger a desktop notification with a custom title, message, and severity level (info, warn, error). This is useful for providing immediate feedback on background task completion or issues. It is categorised as a Execute tool in the Subconductor MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Subconductor MCP server in PolicyLayer and add a rule for alert: 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 Subconductor. Nothing to install.
alert 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 alert 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 alert. 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.
alert is provided by the Subconductor MCP server (paulbenchea/mcp-subconductor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
alert is one line of Subconductor's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →