post-schedule
Schedule a Nostr event for future publication. Signs the event now and queues it on disk. Use nostr-bray publish-scheduled (via cron) to publish when due.
This record as markdown: /tools/dev-forgesworn-bray/post-schedule.md
What post-schedule does on Nostr Bray
AI agents use post-schedule 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 post-schedule is rated Medium
The tool creates/persists data (scheduling an event and signing it) rather than deleting it or moving money. It does not execute arbitrary code—it merely queues a pre-signed event. However, if misused by an AI agent, it could be leveraged to schedule unwanted posts on behalf of a user without immediate visibility.
From the tool's definition Tool creates and stores a Nostr event for future publication: 'Schedule a Nostr event for future publication. Signs the event now and queues it on disk.' This is a reversible write operation (the scheduled event can be canceled or removed before publication).
Attacks that exploit this kind of access
The rule that runs post-schedule 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 post-schedule, this is the rule to start with:
post-schedule 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 post-schedule call is checked against it from then on.
Questions about post-schedule
Schedule a Nostr event for future publication. Signs the event now and queues it on disk. Use nostr-bray publish-scheduled (via cron) to publish when due. 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 post-schedule: 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.
post-schedule 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 post-schedule 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 post-schedule. 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.
post-schedule 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