This record as markdown: /tools/dev-forgesworn-bray/safety-activate.md
What safety-activate does on Nostr Bray
AI agents use safety-activate 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 safety-activate is rated Medium
This tool modifies identity configuration, which is a reversible state change (switching between configurations). It does not execute code or trigger external operations based on arbitrary arguments (Execute), does not permanently delete data (Destructive), and does not involve financial transactions (Financial).
From the tool's definition Tool name 'safety-activate' combined with description 'Switch to an alternative identity configuration' indicates modification of identity state.
Attacks that exploit this kind of access
The rule that runs safety-activate 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 safety-activate, this is the rule to start with:
safety-activate 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 safety-activate call is checked against it from then on.
Questions about safety-activate
Switch to an alternative identity configuration. 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 safety-activate: 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.
safety-activate 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 safety-activate 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 safety-activate. 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.
safety-activate 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