list-pin-read

Read your pinned events list (NIP-51, kind 10001).

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/list-pin-read.md

WHAT IT DOES

What list-pin-read does on Nostr Bray

AI agents call list-pin-read 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 list-pin-read is rated Low

This tool queries and retrieves a user's pinned events from their Nostr profile without creating, modifying, or deleting any data. It is a straightforward read operation with minimal security risk—the worst outcome is information disclosure of the user's own pinned content.

From the tool's definition Tool name contains 'read' and description states 'Read your pinned events list'. The action retrieves existing data (NIP-51 pinned events) with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list-pin-read Allowed

list-pin-read 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": {
    "list-pin-read": {}
  }
}

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 list-pin-read call is checked against it from then on.

FAQ

Questions about list-pin-read

What does the list-pin-read tool do? +

Read your pinned events list (NIP-51, kind 10001). 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 list-pin-read? +

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

list-pin-read is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list-pin-read? +

Yes. Add a rate_limit block to the list-pin-read 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 list-pin-read completely? +

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

list-pin-read 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

aiva_list_affiliates on AIVA MCP Server →claude_read_file on Claude Bridge →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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