Get transactions with comprehensive information retention
AI agents call get_past_transactions to retrieve information from Odos MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries past transaction history from the blockchain/DeFi portfolio. There are no side effects, no state changes, no code execution, and no financial operations being initiated. The 'information retention' phrasing indicates comprehensive data retrieval rather than any form of action. Even in a DeFi context, querying transaction history is a passive read operation.
From the tool's definition Tool name 'get_past_transactions' with description 'Get transactions with comprehensive information retention' describes retrieval of historical transaction data with no modification or execution capability.
Attacks that exploit this kind of access
Get transactions with comprehensive information retention. It is categorised as a Read tool in the Odos MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Odos MCP Server MCP server in PolicyLayer and add a rule for get_past_transactions: 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 Odos MCP Server. Nothing to install.
get_past_transactions 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_past_transactions 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_past_transactions. 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_past_transactions is provided by the Odos MCP Server MCP server (odos-xyz/odos-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 →