nostr_get_profile

Get a Nostr profile (kind:0 metadata) for any public key.

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-get-profile.md

WHAT IT DOES

What nostr_get_profile does on Aibtc

AI agents call nostr_get_profile 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_get_profile is rated Low

This tool queries and returns existing profile data from the Nostr protocol without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security risk—the worst outcome of misuse would be retrieving publicly available profile information, which carries no blast radius.

From the tool's definition Tool retrieves Nostr profile metadata (kind:0) for a public key with no side effects described. The verb 'Get' and absence of modification/deletion capabilities indicate a pure retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

nostr_get_profile Allowed

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

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

FAQ

Questions about nostr_get_profile

What does the nostr_get_profile tool do? +

Get a Nostr profile (kind:0 metadata) for any public key. 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_get_profile? +

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

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

Can I rate-limit nostr_get_profile? +

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

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

nostr_get_profile 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_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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