Get detailed statistics and information for a specific THORChain liquidity pool
AI agents call get-pool-detail to retrieve information from THORChain MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query operation that retrieves and returns blockchain data about liquidity pools. There are no side effects, no data modification, no code execution, and no financial transactions. The worst misuse scenario is information disclosure or data exfiltration, which poses minimal direct risk compared to other categories.
From the tool's definition Tool retrieves 'detailed statistics and information for a specific THORChain liquidity pool' with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get detailed statistics and information for a specific THORChain liquidity pool. It is categorised as a Read tool in the THORChain MCP Server MCP Server, which means it retrieves data without modifying state.
Register the THORChain MCP Server MCP server in PolicyLayer and add a rule for get-pool-detail: 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 THORChain MCP Server. Nothing to install.
get-pool-detail 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-pool-detail 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-pool-detail. 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-pool-detail is provided by the THORChain MCP Server MCP server (missionsquad/mcp-thorchain). 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 →