Returns historical data from the Kaskad Protocol subgraph: recent liquidations, current market APY snapshots,
AI agents call getHistory to retrieve information from Kaskad Protocol 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 tool that retrieves historical information and market snapshots from a subgraph. It has no side effects, does not execute transactions, does not modify state, and does not move funds. While it operates in a DeFi context, the tool itself only fetches and returns data without triggering any financial actions or state changes.
From the tool's definition Tool name 'getHistory' and description indicates it 'Returns historical data from the Kaskad Protocol subgraph: recent liquidations, current market APY snapshots' — purely data retrieval with no modification, execution, or financial operations.
Attacks that exploit this kind of access
Returns historical data from the Kaskad Protocol subgraph: recent liquidations, current market APY snapshots,. It is categorised as a Read tool in the Kaskad Protocol MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kaskad Protocol MCP Server MCP server in PolicyLayer and add a rule for getHistory: 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 Kaskad Protocol MCP Server. Nothing to install.
getHistory 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 getHistory 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 getHistory. 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.
getHistory is provided by the Kaskad Protocol MCP Server MCP server (kaskad-lending/kaskad-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 →