AI agents call pushover_validate_user to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
device | string | — | Optional: validate only for a specific device name |
user_key | string | Yes | |
app_token | string | Yes |
Parameters from the server's own tool schema.
This tool performs a lookup/query operation that returns information about a user account and associated devices. It does not create, modify, delete, or execute any operations — it only reads and validates existing data. The blast radius is low since it only exposes already-accessible account information that a legitimate user would already know.
From the tool's definition Tool description states 'Validate a Pushover user or group key and list their registered devices' — it retrieves and queries user validation status and device information with no modification or destructive capability.
Attacks that exploit this kind of access
Validate a Pushover user or group key and list their registered devices. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
pushover_validate_user accepts 3 parameters: device, user_key, app_token. Required: 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_validate_user: 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_validate_user 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_validate_user 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_validate_user. 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_validate_user 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 →