crow_create_notification
Create a notification for the user. Use for reminders, alerts, or any information the user should see in the Crow
This record as markdown: /tools/kh0pper-crow/crow-create-notification.md
What crow_create_notification does on Crow
AI agents use crow_create_notification to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why crow_create_notification is rated Medium
This tool creates new data (notifications) within the Crow system without deleting or destructively modifying existing data. The 'create' verb and action of generating notifications places it in the Write category. Severity is medium because malicious misuse could spam users with false notifications, disrupting workflow or trust, but the impact is reversible and non-destructive to core project data.
From the tool's definition Tool name uses 'create', and description states 'Create a notification for the user', indicating irreversible creation of new notification data in the system.
Attacks that exploit this kind of access
The rule that runs crow_create_notification safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_create_notification, this is the rule to start with:
crow_create_notification stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_create_notification call is checked against it from then on.
Questions about crow_create_notification
Create a notification for the user. Use for reminders, alerts, or any information the user should see in the Crow. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for crow_create_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 Crow. Nothing to install.
crow_create_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 crow_create_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 crow_create_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.
crow_create_notification is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue