list_x402_endpoints

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/list-x402-endpoints.md

WHAT IT DOES

What list_x402_endpoints does on Aibtc

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

Tool only queries and lists endpoint information without modifying, executing, or affecting system state.

From the tool's definition List x402 API endpoints, read live from OpenAPI specs, registry.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_x402_endpoints Allowed

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

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

FAQ

Questions about list_x402_endpoints

What does the list_x402_endpoints tool do? +

List x402 API endpoints. x402.aibtc.com and stx402.com are read live from their OpenAPI specs; the stx402.com directory lists x402 endpoints registered by third parties. Sources: - x402.biwas.xyz: DeFi analytics, market data, wallet analysis, Zest/ALEX protocols - x402.aibtc.com: AI inference, Stacks utilities, hashing, storage (live) - stx402.com: x402 endpoint registry, agent registry (ERC-8004), links (live) - aibtc.com: Inbox messaging - directory: third-party endpoints registered at stx402.com (live, mainnet). Unverified entries are hidden unless includeUnverified is true — probe before paying. Costs from live specs are tiers (. 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? +

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

Set action: deny in the PolicyLayer 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 (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 366 Aibtc tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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