Get token mappings (wrapped token relationships)
AI agents call alex_get_token_mappings to retrieve information from Stacks AI 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 quasi-static mapping data about token relationships, likely reference information used to understand how wrapped tokens correspond to their underlying assets. It performs no creation, modification, deletion, execution, or financial transaction. The operation is read-only information retrieval, consistent with tools like alex_get_all_pools and alex_get_all_token_prices on the same server.
From the tool's definition Tool name 'alex_get_token_mappings' with description 'Get token mappings (wrapped token relationships)' indicates a retrieval operation.
Attacks that exploit this kind of access
Get token mappings (wrapped token relationships). It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for alex_get_token_mappings: 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 Stacks AI MCP Server. Nothing to install.
alex_get_token_mappings 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 alex_get_token_mappings 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 alex_get_token_mappings. 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.
alex_get_token_mappings is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). 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 →