Send a notification to a user
AI agents use send-notification to create or update resources in NestJS MCP Server Module — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NestJS MCP Server Module environment.
This tool creates new notifications, which is a reversible data modification. It does not execute arbitrary code, delete data, or move money. However, the medium severity reflects that misuse could spam users, trigger unwanted communications, or be exploited for social engineering if an AI agent has unrestricted access to send notifications to any user without proper authorization checks.
From the tool's definition Tool name 'send-notification' and description 'Send a notification to a user' indicate a write operation that creates/modifies user notification state.
Attacks that exploit this kind of access
Send a notification to a user. It is categorised as a Write tool in the NestJS MCP Server Module MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NestJS MCP Server Module 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 NestJS MCP Server Module. Nothing to install.
send-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-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 NestJS MCP Server Module MCP server (rekog-labs/mcp-nest). 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 →