pushover_cancel_emergency · UnClick MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

Parameter	Type	Required
`receipt`	string	Yes
`user_key`	string	Yes
`app_token`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why pushover_cancel_emergency needs a policy

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

Recommended rule Ready

Verdict

pushover_cancel_emergency Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pushover_cancel_emergency": {
      "limits": [
        {
          "counter": "pushover_cancel_emergency_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches UnClick, so you can run agents against it safely.

FAQ

Questions about pushover_cancel_emergency

What does the pushover_cancel_emergency tool do? +

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.

What parameters does pushover_cancel_emergency accept? +

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.

How do I enforce a policy on pushover_cancel_emergency? +

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.

What risk level is pushover_cancel_emergency? +

pushover_cancel_emergency is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pushover_cancel_emergency? +

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.

How do I block pushover_cancel_emergency completely? +

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.

What MCP server provides pushover_cancel_emergency? +

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.