Send a proactive notification to the operator interface, optionally with one follow-up action button. Use this for alerts or prompts that should remain visible in the UI; this is better than sint__speak when the operator needs something clickable or persistent. Returns a JSON confirmation with th...
AI agents use sint__notify to create or update resources in SINT Protocol — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SINT Protocol environment.
This tool creates new notifications in the operator interface—a reversible write operation. It has no destructive effects, does not execute external code or shell commands, does not move money, and does not delete data. The blast radius of misuse is minimal: a spam or misleading notification is annoying but easily dismissed and does not compromise system integrity or cause permanent harm.
From the tool's definition Tool sends/creates a notification in the operator interface with optional action button and returns JSON confirmation. The description explicitly states it sends a 'proactive notification' and creates persistent UI elements.
Documented attack patterns abuse exactly the kind of access sint__notify gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SINT Protocol, and nothing reaches the server without passing your rules. This is the rule we recommend for sint__notify:
{
"version": "1",
"default": "deny",
"tools": {
"sint__notify": {
"limits": [
{
"counter": "sint__notify_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sint__notify 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.
Free to start. No card required.
Send a proactive notification to the operator interface, optionally with one follow-up action button. Use this for alerts or prompts that should remain visible in the UI; this is better than sint__speak when the operator needs something clickable or persistent. Returns a JSON confirmation with the notification timestamp and echoed message. It is categorised as a Write tool in the SINT Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SINT Protocol MCP server in PolicyLayer and add a rule for sint__notify: 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 SINT Protocol. Nothing to install.
sint__notify 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 sint__notify 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 sint__notify. 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.
sint__notify is provided by the SINT Protocol MCP server (sint-ai/sint-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SINT Protocol, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 SINT Protocol tools catalogued and risk-classified — across an index of 43,000+ MCP servers.