dispatch-failure
Report that a dispatch task failed after you attempted it. Use when you tried to complete the task but encountered errors. Optionally include partial results so work is not lost.
This record as markdown: /tools/dev-forgesworn-bray/dispatch-failure.md
What dispatch-failure does on Nostr Bray
AI agents use dispatch-failure to create or update resources in Nostr Bray, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nostr Bray environment.
Why dispatch-failure is rated Medium
The tool writes a failure report for a dispatch task, potentially including partial results. This is a Write operation (creating/updating a status record) rather than Destructive or Execute. Misuse could corrupt task state or cause work to be incorrectly marked as failed, hence medium severity.
From the tool's definition 'Report that a dispatch task failed after you attempted it' and 'Optionally include partial results so work is not lost' — this writes a failure status/report record to the system
Attacks that exploit this kind of access
The rule that runs dispatch-failure safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nostr Bray, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dispatch-failure, this is the rule to start with:
dispatch-failure stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nostr Bray, apply this rule, and every dispatch-failure call is checked against it from then on.
Questions about dispatch-failure
Report that a dispatch task failed after you attempted it. Use when you tried to complete the task but encountered errors. Optionally include partial results so work is not lost. It is categorised as a Write tool in the Nostr Bray MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for dispatch-failure: 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 Nostr Bray. Nothing to install.
dispatch-failure is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dispatch-failure 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 dispatch-failure. 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.
dispatch-failure is provided by the Nostr Bray MCP server (nostr-bray). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nostr Bray, and thousands of servers like it.
This server
Across the catalogue