nostr_search_tags

Search Nostr for kind:1 notes matching hashtags using NIP-12 #t filter.

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-search-tags.md

WHAT IT DOES

What nostr_search_tags does on Aibtc

AI agents call nostr_search_tags 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_search_tags is rated Low

This tool retrieves data from the Nostr protocol (a decentralized social network) by applying a hashtag filter. It has no capability to modify, delete, or execute code. The operation is a straightforward query that returns matching notes without any reversible or irreversible modifications.

From the tool's definition Tool name and description indicate a search operation: 'Search Nostr for kind:1 notes matching hashtags'. The use of 'search' and querying against a filter are read-only operations with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

nostr_search_tags Allowed

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

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

FAQ

Questions about nostr_search_tags

What does the nostr_search_tags tool do? +

Search Nostr for kind:1 notes matching hashtags using NIP-12 #t filter. 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_search_tags? +

Register the Aibtc MCP server in PolicyLayer and add a rule for nostr_search_tags: 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_search_tags? +

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

Can I rate-limit nostr_search_tags? +

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

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

nostr_search_tags 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

get_cocktail_by_tags on Cocktails RAG MCP Server →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

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