pillar_direct_resolve_recipient

Resolve a recipient before sending. Resolves BNS names (.btc) via backend,

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/pillar-direct-resolve-recipient.md

WHAT IT DOES

What pillar_direct_resolve_recipient does on Aibtc

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

This tool performs a lookup/resolution of a BNS name to an address. It is a read/query operation with no side effects — it simply resolves a name before a transaction, not performing the transaction itself.

From the tool's definition Resolve a recipient before sending. Resolves BNS names (.btc) via backend

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pillar_direct_resolve_recipient Allowed

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

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

FAQ

Questions about pillar_direct_resolve_recipient

What does the pillar_direct_resolve_recipient tool do? +

Resolve a recipient before sending. Resolves BNS names (.btc) via backend,. 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 pillar_direct_resolve_recipient? +

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

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

Can I rate-limit pillar_direct_resolve_recipient? +

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

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

pillar_direct_resolve_recipient 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

The MCP Attack Database →

Guides

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