dispatch-status
Send a status update to collaborators. Use to broadcast availability (e.g.
This record as markdown: /tools/dev-forgesworn-bray/dispatch-status.md
What dispatch-status does on Nostr Bray
AI agents use dispatch-status 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-status is rated Medium
This tool sends/publishes a status message to other users (collaborators), which is a write operation creating new content on the Nostr network. It does not delete, execute code, or involve financial transactions. Severity is medium because it broadcasts messages to other users, which could be misused to send misleading availability signals, but the blast radius is limited.
From the tool's definition 'Send a status update to collaborators. Use to broadcast availability'
Attacks that exploit this kind of access
The rule that runs dispatch-status 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-status, this is the rule to start with:
dispatch-status 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-status call is checked against it from then on.
Questions about dispatch-status
Send a status update to collaborators. Use to broadcast availability (e.g. 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-status: 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-status 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-status 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-status. 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-status 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