calendar-create
Create a calendar event (NIP-52). Auto-detects date-based (kind 31922, YYYY-MM-DD) vs time-based (kind 31923, ISO datetime). Returns the signed event and publish result.
This record as markdown: /tools/dev-forgesworn-bray/calendar-create.md
What calendar-create does on Nostr Bray
AI agents use calendar-create 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 calendar-create is rated Medium
This tool creates new calendar events in a Nostr network, modifying the user's published data. It is reversible (events can be deleted or superseded), so it is Write not Destructive. Severity is medium because calendar spam or injection of false events could degrade user experience and trust, but the blast radius is limited to calendar data without direct financial, operational, or system-wide impact.
From the tool's definition Tool explicitly 'Create[s] a calendar event' via NIP-52 (Nostr event protocol). The description confirms data creation: 'Create a calendar event' with 'Returns the signed event and publish result' indicating persistent storage/broadcast.
Attacks that exploit this kind of access
The rule that runs calendar-create 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 calendar-create, this is the rule to start with:
calendar-create 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 calendar-create call is checked against it from then on.
Questions about calendar-create
Create a calendar event (NIP-52). Auto-detects date-based (kind 31922, YYYY-MM-DD) vs time-based (kind 31923, ISO datetime). Returns the signed event and publish result. 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 calendar-create: 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.
calendar-create 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 calendar-create 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 calendar-create. 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.
calendar-create 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