This record as markdown: /tools/dev-forgesworn-bray/signet-policy-check.md
What signet-policy-check does on Nostr Bray
AI agents call signet-policy-check to retrieve information from Nostr Bray without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why signet-policy-check is rated Low
This tool performs a read-only verification check against a policy to determine if a given public key meets community requirements. No data is created, modified, deleted, or financial operations are performed. The operation is purely informational with no side effects.
From the tool's definition Tool name includes 'check' and description states 'Check whether a pubkey satisfies a community' — a query operation that retrieves or verifies compliance status without modifying data.
Attacks that exploit this kind of access
The rule that runs signet-policy-check 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-policy-check, this is the rule to start with:
signet-policy-check is read-only, so it stays allowed. 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-policy-check call is checked against it from then on.
Questions about signet-policy-check
Check whether a pubkey satisfies a community\. It is categorised as a Read tool in the Nostr Bray MCP Server, which means it retrieves data without modifying state.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for signet-policy-check: 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-policy-check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the signet-policy-check 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-policy-check. 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-policy-check 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