React to an event (kind 7)
AI agents use reactToEvent to create or update resources in Nostr Tools for AI Agents — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nostr Tools for AI Agents environment.
This tool creates and publishes data (a reaction event) to a decentralized network. While reactions are reversible through deleteEvent and do not involve financial transactions or irreversible destruction, they permanently broadcast user-generated content to Nostr relays.
From the tool's definition Tool creates a new event (kind 7 reaction event) on the Nostr protocol. The description indicates it 'React to an event (kind 7)', which in Nostr publishes a new reaction event to the network—a creation/modification action with side effects.
Attacks that exploit this kind of access
React to an event (kind 7). It is categorised as a Write tool in the Nostr Tools for AI Agents MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nostr Tools for AI Agents MCP server in PolicyLayer and add a rule for reactToEvent: 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 Tools for AI Agents. Nothing to install.
reactToEvent 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 reactToEvent 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 reactToEvent. 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.
reactToEvent is provided by the Nostr Tools for AI Agents MCP server (jorgenclaw/nostr-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →