pushover_get_receipt
Get acknowledgment status for an emergency Pushover notification.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pushover-get-receipt.md
What pushover_get_receipt does on UnClick
AI agents call pushover_get_receipt to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
receipt | string | Yes | Receipt token returned from an emergency notification |
app_token | string | Yes |
Parameters from the server's own tool schema.
Why pushover_get_receipt is rated Low
This tool retrieves or queries data (acknowledgment status) without modifying, executing, deleting, or moving money. It has no side effects beyond reading notification metadata. The low severity reflects minimal blast radius if misused—an agent could only retrieve receipt information for notifications, not create, send, or delete them.
From the tool's definition Tool name 'pushover_get_receipt' and description 'Get acknowledgment status for an emergency Pushover notification' indicate a retrieval operation that queries the status of a previously sent notification.
Attacks that exploit this kind of access
The rule that runs pushover_get_receipt 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_get_receipt, this is the rule to start with:
pushover_get_receipt is read-only, so it stays allowed. 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_get_receipt call is checked against it from then on.
Questions about pushover_get_receipt
Get acknowledgment status for an emergency Pushover notification. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
pushover_get_receipt accepts 2 parameters: receipt, app_token. Required: receipt, 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_get_receipt: 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_get_receipt is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pushover_get_receipt 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_get_receipt. 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_get_receipt 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