pushover_list_sounds
List all available notification sounds in Pushover.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/pushover-list-sounds.md
What pushover_list_sounds does on UnClick
AI agents call pushover_list_sounds 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 |
|---|---|---|---|
app_token | string | Yes |
Parameters from the server's own tool schema.
Why pushover_list_sounds is rated Low
This tool retrieves a static list of available sounds from the Pushover notification service. It performs a read-only query with no side effects, no execution of arbitrary code, and no destructive or financial operations. The blast radius of misuse is minimal—an agent could only enumerate available sounds, which is informational data with no security or operational impact.
From the tool's definition Tool name 'pushover_list_sounds' combined with description 'List all available notification sounds in Pushover' indicates a query operation with no data modification, creation, or deletion.
Attacks that exploit this kind of access
The rule that runs pushover_list_sounds 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_list_sounds, this is the rule to start with:
pushover_list_sounds 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_list_sounds call is checked against it from then on.
Questions about pushover_list_sounds
List all available notification sounds in Pushover. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
pushover_list_sounds accepts 1 parameter: app_token. Required: 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_list_sounds: 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_list_sounds 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_list_sounds 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_list_sounds. 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_list_sounds 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