List all tradable tokens on CSPR.trade with optional fiat pricing
AI agents call get_tokens to retrieve information from CSPR[dot]trade MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about available tokens and their pricing. It performs no write operations, does not execute trades or smart contracts, and has no destructive or financial side effects. The blast radius of misuse is minimal—an agent could only retrieve token listings, which are public information on a decentralized exchange.
From the tool's definition Tool name 'get_tokens' and description 'List all tradable tokens on CSPR.trade with optional fiat pricing' indicate a read-only operation that retrieves and displays public data without modifying state or executing transactions.
Attacks that exploit this kind of access
List all tradable tokens on CSPR.trade with optional fiat pricing. It is categorised as a Read tool in the CSPR[dot]trade MCP MCP Server, which means it retrieves data without modifying state.
Register the CSPR[dot]trade MCP server in PolicyLayer and add a rule for get_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 CSPR[dot]trade MCP. Nothing to install.
get_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_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_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_tokens is provided by the CSPR[dot]trade MCP server (make-software/cspr-trade-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 →