list_x402_endpoints

List known x402 API endpoints from ${ALL_SOURCES}. 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 ...

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

Why list_x402_endpoints is rated Low

This tool retrieves a list of available API endpoints—a read operation. However, the severity is elevated to 'medium' rather than 'low' because the listed endpoints include paid API calls (x402 protocol) and direct Stacks blockchain transaction capabilities (transfer STX, deploy contracts). An agent discovering this list could then use other tools to execute financial transactions or blockchain operations.

From the tool's definition Tool name 'list_x402_endpoints' and description 'List known x402 API endpoints from ${ALL_SOURCES}' indicate data retrieval with no modification or deletion.

Questions about list_x402_endpoints

What does the list_x402_endpoints tool do? +

List known x402 API endpoints from ${ALL_SOURCES}. 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? +

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.

More on Aibtc, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Aibtc's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.