获取支持的代币列表
AI agents call get_supported_tokens to retrieve information from Blockchain Payment MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static or semi-static reference data about which tokens are supported on the blockchain payment server. It performs a query with no side effects, no financial obligation, and no irreversible actions. It is purely informational, placing it clearly in the Read category with low severity.
From the tool's definition Tool name is 'get_supported_tokens' and description translates to 'Get list of supported tokens'. The verb 'get' and 'list' indicate retrieval only. No modification, deletion, or execution of transactions occurs.
Attacks that exploit this kind of access
获取支持的代币列表. It is categorised as a Read tool in the Blockchain Payment MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Blockchain Payment MCP Server MCP server in PolicyLayer and add a rule for get_supported_tokens: 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 Blockchain Payment MCP Server. Nothing to install.
get_supported_tokens is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_supported_tokens 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.
Set action: deny in the PolicyLayer policy for get_supported_tokens. 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.
get_supported_tokens is provided by the Blockchain Payment MCP Server MCP server (logos-42/blockchain-payment-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →