Create an unsigned Nostr event of any kind
AI agents use createNostrEvent to create or update resources in Nostr_AI_Tools_Jorgenclaw — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nostr_AI_Tools_Jorgenclaw environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
kind | number | — | Event kind number |
tags | array | — | Event tags |
content | string | — | Event content |
Parameters from the server's own tool schema.
This is a Write operation because it creates data (unsigned Nostr events) that will be recorded on the Nostr network. While the event is unsigned (so it cannot be directly published by the signer), the tool enables creation of new event objects.
From the tool's definition Tool creates Nostr events, which are data structures recorded on the Nostr network. The description states 'Create an unsigned Nostr event of any kind', indicating it generates new data records.
Risk signalsAccepts raw HTML/template content (content)
Documented attack patterns abuse exactly the kind of access createNostrEvent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nostr_AI_Tools_Jorgenclaw, and nothing reaches the server without passing your rules. This is the rule we recommend for createNostrEvent:
{
"version": "1",
"default": "deny",
"tools": {
"createNostrEvent": {
"limits": [
{
"counter": "createnostrevent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createNostrEvent 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.
Free to start. No card required.
Create an unsigned Nostr event of any kind. It is categorised as a Write tool in the Nostr_AI_Tools_Jorgenclaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
createNostrEvent accepts 3 parameters: kind, tags, content. The full parameter table on this page comes from the server's own tool schema.
Register the Nostr_AI_Tools_Jorgenclaw MCP server in PolicyLayer and add a rule for createNostrEvent: 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_AI_Tools_Jorgenclaw. Nothing to install.
createNostrEvent 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 createNostrEvent 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 createNostrEvent. 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.
createNostrEvent is provided by the Nostr_AI_Tools_Jorgenclaw MCP server (Nostr_AI_Tools_Jorgenclaw/Nostr_AI_Tools_Jorgenclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nostr_AI_Tools_Jorgenclaw, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Nostr_AI_Tools_Jorgenclaw tools catalogued and risk-classified — across an index of 43,000+ MCP servers.