signet-challenge
Publish a kind 31000 challenge event against a verifier suspected of misconduct. Provide a reason code and optional supporting evidence text. Use
This record as markdown: /tools/dev-forgesworn-bray/signet-challenge.md
What signet-challenge does on Nostr Bray
AI agents use signet-challenge to create or update resources in Nostr Bray, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nostr Bray environment.
Why signet-challenge is rated Medium
This tool publishes a public challenge event on the Nostr network targeting a specific verifier, which is a write operation (creating a new event). However, it has high severity because it can be misused to falsely accuse or publicly defame verifiers, causing reputational harm. It is reversible in principle (events can be deleted on some relays) but the social damage from a misconduct accusation may be lasting.
From the tool's definition Publish a kind 31000 challenge event against a verifier suspected of misconduct. Provide a reason code and optional supporting evidence text.
Attacks that exploit this kind of access
The rule that runs signet-challenge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nostr Bray, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For signet-challenge, this is the rule to start with:
signet-challenge 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 Nostr Bray, apply this rule, and every signet-challenge call is checked against it from then on.
Questions about signet-challenge
Publish a kind 31000 challenge event against a verifier suspected of misconduct. Provide a reason code and optional supporting evidence text. Use. It is categorised as a Write tool in the Nostr Bray MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for signet-challenge: 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 Bray. Nothing to install.
signet-challenge 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 signet-challenge 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 signet-challenge. 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.
signet-challenge is provided by the Nostr Bray MCP server (nostr-bray). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nostr Bray, and thousands of servers like it.
This server
Across the catalogue