pushover_cancel_emergency
Cancel an outstanding emergency Pushover notification before it expires.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pushover-cancel-emergency.md
What pushover_cancel_emergency does on UnClick
AI agents use pushover_cancel_emergency 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 |
|---|---|---|---|
receipt | string | Yes | |
user_key | string | Yes | |
app_token | string | Yes |
Parameters from the server's own tool schema.
Why pushover_cancel_emergency is rated Medium
This tool cancels (stops) an active emergency notification. While it is a modification of an existing resource (stopping a repeating alert), it is reversible in the sense that a new emergency notification can be resent. It does not delete data permanently, execute code, or move money. The most appropriate category is Write (modifying/cancelling an in-flight notification).
From the tool's definition Cancel an outstanding emergency Pushover notification before it expires
Attacks that exploit this kind of access
The rule that runs pushover_cancel_emergency safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pushover_cancel_emergency, this is the rule to start with:
pushover_cancel_emergency 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 UnClick, apply this rule, and every pushover_cancel_emergency call is checked against it from then on.
Questions about pushover_cancel_emergency
Cancel an outstanding emergency Pushover notification before it expires. 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_cancel_emergency accepts 3 parameters: receipt, user_key, app_token. Required: receipt, 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_cancel_emergency: 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_cancel_emergency 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_cancel_emergency 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_cancel_emergency. 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_cancel_emergency 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue