calendar-read

Fetch calendar events (NIP-52, kinds 31922 + 31923) by author and/or date range. Accepts any identifier for author: name, NIP-05, npub, or hex pubkey.

SERVERNostr Bray SOURCEnostr-bray

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-forgesworn-bray/calendar-read.md

WHAT IT DOES

What calendar-read does on Nostr Bray

AI agents call calendar-read 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.

RISK

Why calendar-read is rated Low

This tool retrieves calendar event data from a Nostr protocol store (NIP-52 event kinds) filtered by author and date range. It performs a read-only query operation with no side effects, reversibility concerns, or ability to modify, delete, or execute code. The ability to query by multiple author identifier formats (name, NIP-05, npub, hex pubkey) does not elevate the risk—it remains a data retrieval operation.

From the tool's definition Tool name contains 'read'; description states 'Fetch calendar events' with no mention of modification, deletion, or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs calendar-read 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-read, this is the rule to start with:

calendar-read Allowed

calendar-read is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calendar-read": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nostr Bray, apply this rule, and every calendar-read call is checked against it from then on.

FAQ

Questions about calendar-read

What does the calendar-read tool do? +

Fetch calendar events (NIP-52, kinds 31922 + 31923) by author and/or date range. Accepts any identifier for author: name, NIP-05, npub, or hex pubkey. It is categorised as a Read tool in the Nostr Bray MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on calendar-read? +

Register the Nostr Bray MCP server in PolicyLayer and add a rule for calendar-read: 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.

What risk level is calendar-read? +

calendar-read is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit calendar-read? +

Yes. Add a rate_limit block to the calendar-read 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.

How do I block calendar-read completely? +

Set action: deny in the PolicyLayer policy for calendar-read. 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.

What MCP server provides calendar-read? +

calendar-read 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.

KEEP EXPLORING

More on Nostr Bray, and thousands of servers like it.

This server

All 240 Nostr Bray tools →

Across the catalogue

claude_read_file on Claude Bridge →get_ctf_calendar on CTFtime MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →