canary-session-verify

Verify a spoken word against an active CANARY session.

SERVERNostr Bray SOURCEnostr-bray

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-forgesworn-bray/canary-session-verify.md

WHAT IT DOES

What canary-session-verify does on Nostr Bray

AI agents call canary-session-verify 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.

RISK

Why canary-session-verify is rated Low

The tool performs a verification/read operation, checking a spoken word against an existing session state. This is a query/validation action with no apparent data mutation, deletion, or financial implications. Confidence is moderate because the description is sparse and doesn't clarify whether a failed or successful verification triggers any downstream state changes.

From the tool's definition 'Verify a spoken word against an active CANARY session' — verification/checking operation with no apparent side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs canary-session-verify 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 canary-session-verify, this is the rule to start with:

canary-session-verify Allowed

canary-session-verify is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "canary-session-verify": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nostr Bray, apply this rule, and every canary-session-verify call is checked against it from then on.

FAQ

Questions about canary-session-verify

What does the canary-session-verify tool do? +

Verify a spoken word against an active CANARY session. It is categorised as a Read tool in the Nostr Bray MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on canary-session-verify? +

Register the Nostr Bray MCP server in PolicyLayer and add a rule for canary-session-verify: 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.

What risk level is canary-session-verify? +

canary-session-verify is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit canary-session-verify? +

Yes. Add a rate_limit block to the canary-session-verify 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.

How do I block canary-session-verify completely? +

Set action: deny in the PolicyLayer policy for canary-session-verify. 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.

What MCP server provides canary-session-verify? +

canary-session-verify 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.

KEEP EXPLORING

More on Nostr Bray, and thousands of servers like it.

This server

All 240 Nostr Bray tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →