trust-spoken-verify
Verify a spoken token response against the shared secret.
This record as markdown: /tools/dev-forgesworn-bray/trust-spoken-verify.md
What trust-spoken-verify does on Nostr Bray
AI agents invoke trust-spoken-verify to trigger actions in Nostr Bray. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why trust-spoken-verify is rated High
This tool executes a cryptographic or trust verification operation, comparing a token response against a shared secret. It's not a passive read (it validates/authenticates), not a write (it doesn't store data), and not destructive or financial. It falls under Execute as it triggers an authentication/trust evaluation process whose outcome depends on the provided arguments.
From the tool's definition 'Verify a spoken token response against the shared secret' — performs a verification/authentication operation against a secret
Attacks that exploit this kind of access
The rule that runs trust-spoken-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 trust-spoken-verify, this is the rule to start with:
trust-spoken-verify stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 trust-spoken-verify call is checked against it from then on.
Questions about trust-spoken-verify
Verify a spoken token response against the shared secret. It is categorised as a Execute tool in the Nostr Bray MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for trust-spoken-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.
trust-spoken-verify is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the trust-spoken-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.
Set action: deny in the PolicyLayer policy for trust-spoken-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.
trust-spoken-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.
More on Nostr Bray, and thousands of servers like it.
Across the catalogue