Encrypt text with NIP-04 (legacy)
AI agents use encryptNip04 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.
Encryption of text is a reversible data transformation that produces new encrypted content rather than modifying existing state or enabling destructive operations. It has no side effects on the Nostr network and does not execute arbitrary code or trigger external operations.
From the tool's definition Tool name 'encryptNip04' and description 'Encrypt text with NIP-04 (legacy)' indicates data transformation that creates encrypted output without modifying or deleting existing data. NIP-04 is Nostr's legacy encryption standard.
Attacks that exploit this kind of access
Encrypt text with NIP-04 (legacy). 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 encryptNip04: 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.
encryptNip04 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 encryptNip04 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 encryptNip04. 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.
encryptNip04 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 →