AI agents use publish to create or update resources in MCP-NOSTR — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-NOSTR environment.
This tool creates new data (a tweet/post) on the Nostr network. While not destructive or financial, it is a Write operation with high severity because published content on public networks can have reputational, legal, or social consequences if misused by an AI agent (e.g., publishing misleading information, spam, or offensive content).
From the tool's definition Tool name 'publish' and description 'Publish a tweet to Nostr' indicate irreversible creation of content on a public network.
Documented attack patterns abuse exactly the kind of access publish gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-NOSTR, and nothing reaches the server without passing your rules. This is the rule we recommend for publish:
{
"version": "1",
"default": "deny",
"tools": {
"publish": {
"limits": [
{
"counter": "publish_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}publish 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.
Publish a tweet to Nostr. It is categorised as a Write tool in the MCP-NOSTR MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-NOSTR MCP server in PolicyLayer and add a rule for publish: 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 MCP-NOSTR. Nothing to install.
publish 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 publish 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 publish. 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.
publish is provided by the MCP-NOSTR MCP server (pablof7z/tenex-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-NOSTR, 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.
9 MCP-NOSTR tools catalogued and risk-classified — across an index of 43,000+ MCP servers.