pushonly_wake_pusher · UnClick MCP: Risk & Policy

WHAT IT DOES

What pushonly_wake_pusher does on UnClick

AI agents call pushonly_wake_pusher 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.

PARAMETERS

Parameter	Type	Required	Description
`target`	string	—	Human target label such as Boardroom backlog, PR #706, issue #706, or a dispatch ID.
`worker`	string	—	Known worker route such as pinballwake-jobs-worker, Builder, Reviewer, Job Manager, or Heartbeat Seat.
`verifier`	string	—	Optional verifier text copied from IgniteOnly.
`bridge_id`	string	—	Optional trusted bridge ID.
`ignite_id`	string	—	Optional IgniteOnly ID.
`source_id`	string	—	Optional upstream event, dispatch, PR, issue, or wake identifier.
`source_url`	string	—	Optional upstream source URL.
`wake_packet`	object	—	Optional IgniteOnly wake_packet.
`receipt_line`	string	—	Optional compact receipt line copied from IgniteOnly.
`ignite_result`	object	—	Optional output from igniteonly_api or igniteonly_receipt_consumer.
`ignite_status`	string	—	wake_request or escalation_wake_request.
`nudge_trace_id`	string	—	Optional upstream NudgeOnly trace ID.

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why pushonly_wake_pusher needs a policy

Despite the word 'wake' in the name, the description clearly constrains this tool to reading/consuming an input packet and emitting a transformed output, with explicit negations that it does not write persistent state or execute operations. This is consistent with Read category operations (fetch, transform, emit metadata).

From the tool's definition Tool description states it 'consume[s] a verified IgniteOnly wake packet and emit[s] a compact public PushOnly worker envelope' and explicitly clarifies 'It never writes source-of-truth state or executes the work.' This is a consumption and transformation…

Risk signalsHigh parameter count (16 properties)

Attacks that exploit this kind of access

Questions about pushonly_wake_pusher

What does the pushonly_wake_pusher tool do? +

Consume a verified IgniteOnly wake packet and emit a compact public PushOnly worker envelope. It never writes source-of-truth state or executes the work. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does pushonly_wake_pusher accept? +

pushonly_wake_pusher accepts 12 parameters: target, worker, verifier, bridge_id, ignite_id, source_id, source_url, wake_packet, receipt_line, ignite_result, ignite_status, nudge_trace_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on pushonly_wake_pusher? +

Register the UnClick MCP server in PolicyLayer and add a rule for pushonly_wake_pusher: 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 pushonly_wake_pusher? +

pushonly_wake_pusher is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pushonly_wake_pusher? +

Yes. Add a rate_limit block to the pushonly_wake_pusher 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 pushonly_wake_pusher completely? +

Set action: deny in the PolicyLayer policy for pushonly_wake_pusher. 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 pushonly_wake_pusher? +

pushonly_wake_pusher 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.