encode-nsec

Encode a hex private key as a bech32 nsec. WARNING: private key material flows through the MCP transport.

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/encode-nsec.md

WHAT IT DOES

What encode-nsec does on Nostr Bray

AI agents call encode-nsec 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 encode-nsec is rated Low

The tool performs a read/transform operation (encoding a hex private key to bech32 nsec format) with no side effects — it does not write, execute, or delete anything. However, the severity is critical because private key material is exposed through the MCP transport, meaning any misuse, interception, or logging of inputs/outputs could result in complete compromise of a user's cryptographic identity and all…

From the tool's definition 'Encode a hex private key as a bech32 nsec. WARNING: private key material flows through the MCP transport.'

Attacks that exploit this kind of access

RECOMMENDED RULE

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

encode-nsec Allowed

encode-nsec 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": {
    "encode-nsec": {}
  }
}

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 encode-nsec call is checked against it from then on.

FAQ

Questions about encode-nsec

What does the encode-nsec tool do? +

Encode a hex private key as a bech32 nsec. WARNING: private key material flows through the MCP transport. 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 encode-nsec? +

Register the Nostr Bray MCP server in PolicyLayer and add a rule for encode-nsec: 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 encode-nsec? +

encode-nsec is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit encode-nsec? +

Yes. Add a rate_limit block to the encode-nsec 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 encode-nsec completely? +

Set action: deny in the PolicyLayer policy for encode-nsec. 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 encode-nsec? +

encode-nsec 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 →