nostr_read_feed

Read recent kind:1 notes from Nostr relays.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/nostr-read-feed.md

WHAT IT DOES

What nostr_read_feed does on Aibtc

AI agents call nostr_read_feed to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why nostr_read_feed is rated Low

This tool queries and retrieves data (Nostr notes) from relays without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with no capability to alter state or trigger external effects beyond data retrieval.

From the tool's definition Tool name explicitly contains 'read', and description states it 'Read[s] recent kind:1 notes from Nostr relays' — a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nostr_read_feed safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nostr_read_feed, this is the rule to start with:

nostr_read_feed Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every nostr_read_feed call is checked against it from then on.

FAQ

Questions about nostr_read_feed

What does the nostr_read_feed tool do? +

Read recent kind:1 notes from Nostr relays. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on nostr_read_feed? +

Register the Aibtc MCP server in PolicyLayer and add a rule for nostr_read_feed: 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 Aibtc. Nothing to install.

What risk level is nostr_read_feed? +

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

Can I rate-limit nostr_read_feed? +

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

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

nostr_read_feed is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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