nostr_post
Publish a short-text note (kind:1) to Nostr relays.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/nostr-post.md
What nostr_post does on Aibtc
AI agents use nostr_post to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why nostr_post is rated Medium
This tool creates new content (a Nostr note) on a distributed network. It is reversible in the sense that notes can be deleted or users can ignore them, but the act of publishing cannot be undone from the relay perspective. The primary risk is unauthorized posting of content attributed to the user/AI agent, potential spam, or reputational harm.
From the tool's definition Tool description states 'Publish a short-text note (kind:1) to Nostr relays' – the verb 'publish' indicates creating and posting new data to a network.
Attacks that exploit this kind of access
The rule that runs nostr_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nostr_post, this is the rule to start with:
nostr_post 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every nostr_post call is checked against it from then on.
Questions about nostr_post
Publish a short-text note (kind:1) to Nostr relays. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for nostr_post: 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 Aibtc. Nothing to install.
nostr_post 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 nostr_post 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 nostr_post. 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.
nostr_post is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue