list_x402_endpoints

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 call list_x402_endpoints to retrieve information from Aibtc without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON LIST_X402_ENDPOINTS

Even though list_x402_endpoints only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-aibtcdev-mcp-server.yaml

tools:
  list_x402_endpoints:
    rules:
      - action: allow

See the full Aibtc policy for all 288 tools.

// DETAILS

Tool Name list_x402_endpoints

Category Read

MCP Server Aibtc MCP Server

Risk Level Low

// 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 list_x402_endpoints tool do? +

List known x402 API endpoints from x402.biwas.xyz, x402.aibtc.com, stx402.com, aibtc.com. The agent can: 1. Execute x402 endpoints from these sources (paid API calls with automatic payment handling) 2. Execute direct Stacks transactions (transfer STX, call contracts, deploy contracts) Sources: - x402.biwas.xyz: DeFi analytics, market data, wallet analysis, Zest/ALEX protocols - x402.aibtc.com: AI inference, OpenRouter integration, Stacks utilities, hashing, storage - stx402.com: AI services, cryptography, storage, utilities, agent registry - aibtc.com: Inbox messaging system. 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 list_x402_endpoints? +

Add a rule in your Intercept YAML policy under the tools section for list_x402_endpoints. 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 list_x402_endpoints? +

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

Can I rate-limit list_x402_endpoints? +

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

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

list_x402_endpoints 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.

list_x402_endpoints

Enforce policies on Aibtc