snow_send_push_notification
Sends a push notification to mobile devices. Can target specific users, groups, or all users.
This record as markdown: /tools/serac/snow-send-push-notification.md
What snow_send_push_notification does on Serac
AI agents invoke snow_send_push_notification to trigger actions in Serac. 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.
Why snow_send_push_notification is rated High
This tool triggers an external operation (push notification delivery) to mobile devices. It can target all users broadly, creating a high blast radius if misused — e.g., spamming all users or sending misleading notifications. It is not merely writing data to a database; it actively initiates real-time communication to end-user devices, making Execute the appropriate category (more severe than Write).
From the tool's definition Sends a push notification to mobile devices. Can target specific users, groups, or all users.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs snow_send_push_notification safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_send_push_notification, this is the rule to start with:
snow_send_push_notification stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Serac, apply this rule, and every snow_send_push_notification call is checked against it from then on.
Questions about snow_send_push_notification
Sends a push notification to mobile devices. Can target specific users, groups, or all users. It is categorised as a Execute tool in the Serac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Serac MCP server in PolicyLayer and add a rule for snow_send_push_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 Serac. Nothing to install.
snow_send_push_notification 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 snow_send_push_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 snow_send_push_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.
snow_send_push_notification is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
Across the catalogue