dispatch-check
Check for incoming collaboration tasks from trusted Nostr identities. Returns dispatch messages: think tasks, build tasks, results, acks, status updates. Only shows messages from identities in the dispatch trust list, validated for freshness. Defaults to messages received since this session start...
This record as markdown: /tools/dev-forgesworn-bray/dispatch-check.md
What dispatch-check does on Nostr Bray
AI agents call dispatch-check to retrieve information from Nostr Bray without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why dispatch-check is rated Low
This tool reads and queries incoming messages from a trust-filtered stream. It performs retrieval only (no creation, modification, deletion, code execution, or financial operation).
From the tool's definition Tool description states it 'Check[s] for incoming collaboration tasks' and 'Returns dispatch messages' — purely retrieves/queries data with no side effects. The trusted identity filtering and freshness validation are security controls, not operational effects.
Attacks that exploit this kind of access
The rule that runs dispatch-check 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-check, this is the rule to start with:
dispatch-check is read-only, so it stays allowed. 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-check call is checked against it from then on.
Questions about dispatch-check
Check for incoming collaboration tasks from trusted Nostr identities. Returns dispatch messages: think tasks, build tasks, results, acks, status updates. Only shows messages from identities in the dispatch trust list, validated for freshness. Defaults to messages received since this session started (prevents re-processing old tasks). Pass since=0 to see all available messages regardless of age. It is categorised as a Read tool in the Nostr Bray MCP Server, which means it retrieves data without modifying state.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for dispatch-check: 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-check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dispatch-check 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-check. 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-check 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