This record as markdown: /tools/dev-forgesworn-bray/count.md
What count does on Nostr Bray
AI agents call count 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 count is rated Low
This is a read-only query operation. It counts events matching specified criteria but performs no write, deletion, or side-effect operations. The filter parameter allows targeted queries but the output is a simple count metric. Blast radius is minimal—misuse would only surface data counts, not expose sensitive event details or trigger external actions.
From the tool's definition Tool name 'count' and description 'Count events matching a filter on the active identity' indicate a retrieval operation that aggregates or queries existing data without modification.
Attacks that exploit this kind of access
The rule that runs count 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 count, this is the rule to start with:
count 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 count call is checked against it from then on.
Questions about count
Count events matching a filter on the active identity\. 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 count: 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.
count 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 count 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 count. 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.
count 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