Given one token amount, calculate the optimal paired amount for adding liquidity to maintain the pool ratio.
AI agents call optimal_liquidity_amounts 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 performs a read-only calculation based on input parameters to inform liquidity provision decisions. It returns computed values (optimal token amounts) but does not execute transactions, write to blockchain state, or commit financial obligations. The actual liquidity addition would require a separate build_add_liquidity or similar tool. Misuse risk is minimal since the output is advisory only.
From the tool's definition Tool description states it 'calculate[s] the optimal paired amount' — a computational query that retrieves derived data without modifying state, creating transactions, or moving funds.
Attacks that exploit this kind of access
Given one token amount, calculate the optimal paired amount for adding liquidity to maintain the pool ratio. 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 optimal_liquidity_amounts: 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.
optimal_liquidity_amounts 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 optimal_liquidity_amounts 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 optimal_liquidity_amounts. 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.
optimal_liquidity_amounts 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 →