Calculate impermanent loss for a liquidity position
AI agents call get_impermanent_loss 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 liquidity position data. It does not create, modify, delete, or execute financial transactions. It computes impermanent loss metrics for informational purposes, which is a standard Read category function. The word 'Calculate' and 'get' indicate data retrieval with no side effects.
From the tool's definition Tool name is 'get_impermanent_loss' with description 'Calculate impermanent loss for a liquidity position' — a pure calculation/query operation that retrieves analytical data about an existing position without modifying state or executing transactions.
Attacks that exploit this kind of access
Calculate impermanent loss for a liquidity position. 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_impermanent_loss: 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_impermanent_loss 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_impermanent_loss 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_impermanent_loss. 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_impermanent_loss 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 →