Create a new Nostr profile (kind 0)
AI agents use createProfile 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 a new profile record on the Nostr network. Profile creation is reversible (a new event can supersede it) and does not permanently delete data or execute arbitrary code. It modifies the user's presence on the network but does not commit financial transactions or destructively remove data.
From the tool's definition Tool name 'createProfile' and description 'Create a new Nostr profile (kind 0)' indicate data creation. The Nostr protocol uses kind 0 events to represent user profiles; creating one adds a new, reversible entry to the Nostr network.
Attacks that exploit this kind of access
Create a new Nostr profile (kind 0). 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 createProfile: 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.
createProfile 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 createProfile 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 createProfile. 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.
createProfile 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 →