dispatch-ack
Acknowledge receipt of a dispatch task. Tells the sender
This record as markdown: /tools/dev-forgesworn-bray/dispatch-ack.md
What dispatch-ack does on Nostr Bray
AI agents use dispatch-ack 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-ack is rated Medium
The tool sends an acknowledgement back to a sender, which is a write operation (creating/posting a response message). It does not delete data, execute code, or involve financial transactions. Severity is low as it merely confirms receipt of a task.
From the tool's definition 'Acknowledge receipt of a dispatch task. Tells the sender' — sends a confirmation/acknowledgement message
Attacks that exploit this kind of access
The rule that runs dispatch-ack 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-ack, this is the rule to start with:
dispatch-ack 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-ack call is checked against it from then on.
Questions about dispatch-ack
Acknowledge receipt of a dispatch task. Tells the sender. 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-ack: 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-ack 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-ack 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-ack. 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-ack 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