发送系统错误通知
AI agents use send_error_notification to create or update resources in MCP Commute Assistant — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Commute Assistant environment.
This tool creates and transmits data (error notifications) to an external system (DingTalk), which is a write operation. It modifies state by creating new messages/records in the notification system. Severity is medium because misuse could spam users with false error alerts or expose sensitive information in notification content, but notifications are typically reversible and non-destructive.
From the tool's definition Tool name 'send_error_notification' and description '发送系统错误通知' (send system error notification) indicate the tool sends/writes notifications to DingTalk, a messaging platform.
Attacks that exploit this kind of access
发送系统错误通知. It is categorised as a Write tool in the MCP Commute Assistant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Commute Assistant MCP server in PolicyLayer and add a rule for send_error_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 MCP Commute Assistant. Nothing to install.
send_error_notification 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_error_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_error_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_error_notification is provided by the MCP Commute Assistant MCP server (standup-coder/mcp4coder). 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 →