AI agents use pushover_send_notification to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | |
html | boolean | — | |
retry | number | — | Emergency only: retry interval in seconds (min 30) |
sound | string | — | |
title | string | — | |
device | string | — | |
expire | number | — | Emergency only: expiry in seconds (max 10800) |
message | string | Yes | |
priority | number | — | -2 (lowest) to 2 (emergency) |
user_key | string | Yes | |
app_token | string | Yes | |
url_title | string | — |
Parameters from the server's own tool schema.
This tool creates new data (a notification) in an external messaging system and triggers delivery to recipients. It is Write rather than Execute because it performs a bounded, specific operation (sending a notification) rather than arbitrary code execution.
From the tool's definition 'Send a push notification via Pushover' indicates the tool creates and delivers a notification message, which is a write operation that modifies external system state (message queue/delivery system).
Risk signalsAccepts URL/endpoint input (url) · Accepts raw HTML/template content (html) · High parameter count (12 properties)
Attacks that exploit this kind of access
Send a push notification via Pushover. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
pushover_send_notification accepts 12 parameters: url, html, retry, sound, title, device, expire, message, priority, user_key, app_token, url_title. Required: message, user_key, app_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for pushover_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 UnClick. Nothing to install.
pushover_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 pushover_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 pushover_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.
pushover_send_notification is provided by the UnClick MCP server (@unclick/mcp-server). 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 →