Get deposit history with transaction hashes and statuses. Requires authentication.
AI agents call get_deposit_history to retrieve information from Derive MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical deposit data associated with the authenticated user's account. It queries existing transaction information without creating, modifying, deleting, or executing any operations. While it requires authentication and provides access to financial account history, the action itself is non-destructive and non-actionable—it only reads and returns data.
From the tool's definition Tool name 'get_deposit_history' and description 'Get deposit history with transaction hashes and statuses' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get deposit history with transaction hashes and statuses. Requires authentication. It is categorised as a Read tool in the Derive MCP MCP Server, which means it retrieves data without modifying state.
Register the Derive MCP server in PolicyLayer and add a rule for get_deposit_history: 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 Derive MCP. Nothing to install.
get_deposit_history 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_deposit_history 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_deposit_history. 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_deposit_history is provided by the Derive MCP server (solenyaresearch0000/derive-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 →