trust-request-list

Scan received NIP-17 DMs for attestation request payloads.

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/trust-request-list.md

WHAT IT DOES

What trust-request-list does on Nostr Bray

AI agents call trust-request-list 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 trust-request-list is rated Low

This tool queries and lists incoming direct messages (NIP-17 DMs) to find attestation requests. It retrieves data for inspection purposes only, with no side effects—no creation, modification, deletion, or execution of code/commands. It is a read-only scanning operation on the user's message inbox, consistent with the 'Read' category (retrieves or queries data; no side effects).

From the tool's definition Tool name 'trust-request-list' and description 'Scan received NIP-17 DMs for attestation request payloads' indicate retrieval and inspection of existing messages without modification, deletion, or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

trust-request-list Allowed

trust-request-list 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": {
    "trust-request-list": {}
  }
}

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

FAQ

Questions about trust-request-list

What does the trust-request-list tool do? +

Scan received NIP-17 DMs for attestation request payloads. 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 trust-request-list? +

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

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

Can I rate-limit trust-request-list? +

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

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

trust-request-list 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 →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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