pillar_direct_resolve_recipient

Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents use pillar_direct_resolve_recipient to create or modify resources in Aibtc. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON PILLAR_DIRECT_RESOLVE_RECIPIENT

Without a policy, an AI agent could call pillar_direct_resolve_recipient repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Aibtc.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-aibtcdev-mcp-server.yaml

tools:
  pillar_direct_resolve_recipient:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Aibtc policy for all 288 tools.

// DETAILS

Tool Name pillar_direct_resolve_recipient

Category Write

MCP Server Aibtc MCP Server

Risk Level Medium

// MORE AIBTC TOOLS

Financial identity_transfer Financial jingswap_deposit_sbtc Financial jingswap_deposit_stx Financial ordinals_p2p_transfer Financial pillar_direct_withdraw_collateral Financial sbtc_deposit Financial sbtc_transfer Financial sbtc_withdraw

View all 288 tools →

// RELATED READING

// FAQ

What does the pillar_direct_resolve_recipient tool do? +

Resolve a recipient before sending. Resolves BNS names (.btc) via backend, Pillar wallet names via backend, or validates a Stacks address. Use this BEFORE pillar_direct_send to confirm the resolved address with the user.. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pillar_direct_resolve_recipient? +

Add a rule in your Intercept YAML policy under the tools section for pillar_direct_resolve_recipient. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.

What risk level is pillar_direct_resolve_recipient? +

pillar_direct_resolve_recipient is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pillar_direct_resolve_recipient? +

Yes. Add a rate_limit block to the pillar_direct_resolve_recipient rule in your Intercept 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 Intercept 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 (@aibtc/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

pillar_direct_resolve_recipient

Enforce policies on Aibtc