nudgeonly_receipt_bridge

Turn a verified NudgeOnly painpoint into a tiny worker receipt request or WakePass escalation candidate. Deterministic bridge only: no writes, no ownership decision, no completion state.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 120 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/nudgeonly-receipt-bridge.md

WHAT IT DOES

What nudgeonly_receipt_bridge does on UnClick

AI agents call nudgeonly_receipt_bridge 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
`now`	string	—	Optional ISO timestamp used for deterministic TTL checks.
`owner`	string	—	Optional existing owner evidence. The bridge does not invent or decide owners.
`target`	string	—	Optional human target label such as PR #705 or a dispatch ID.
`worker`	string	—	Optional worker override when a trusted lane already named one.
`context`	string	—	Optional local context. Keep it small and non-secret.
`source_id`	string	—	Optional upstream event, dispatch, PR, issue, or wake identifier.
`ack_status`	string	—	Optional ACK status such as missing, stale, received, or blocked.
`created_at`	string	—	Optional ISO timestamp for the source handoff or request.
`event_text`	string	—	Source event, blocker, handoff, or state-card text. Keep it small and non-secret.
`source_url`	string	—	Optional upstream source URL.
`ttl_minutes`	number	—	Minutes before missing ACK/proof becomes an escalation request. Default: 60.
`nudge_result`	object	—	Optional output from nudgeonly_api.

Parameters from the server's own tool schema.

RISK

Why nudgeonly_receipt_bridge is rated Low

This is a read-only transformation utility. Despite the word "bridge" suggesting data movement, the description clearly states it performs no writes and makes no state changes. It retrieves or interprets a "verified NudgeOnly painpoint" and outputs a structured request, similar to a query or formatting operation. No data is modified, deleted, or committed, making it a Read-category tool with low severity.

From the tool's definition "Deterministic bridge only: no writes, no ownership decision, no completion state." The tool explicitly disclaims write, state-change, and decision-making capabilities.

Risk signalsHigh parameter count (18 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nudgeonly_receipt_bridge 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 nudgeonly_receipt_bridge, this is the rule to start with:

nudgeonly_receipt_bridge Allowed

nudgeonly_receipt_bridge is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nudgeonly_receipt_bridge": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every nudgeonly_receipt_bridge call is checked against it from then on.

FAQ

Questions about nudgeonly_receipt_bridge

What does the nudgeonly_receipt_bridge tool do? +

Turn a verified NudgeOnly painpoint into a tiny worker receipt request or WakePass escalation candidate. Deterministic bridge only: no writes, no ownership decision, no completion state. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does nudgeonly_receipt_bridge accept? +

nudgeonly_receipt_bridge accepts 12 parameters: now, owner, target, worker, context, source_id, ack_status, created_at, event_text, source_url, ttl_minutes, nudge_result. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on nudgeonly_receipt_bridge? +

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

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

Can I rate-limit nudgeonly_receipt_bridge? +

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

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

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

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →