transaction_history
Get transaction history
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/transaction-history.md
What transaction_history does on MIDAS Protocol
AI agents call transaction_history to retrieve information from MIDAS Protocol without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
offset | number | — |
Parameters from the server's own tool schema.
Why transaction_history is rated Low
This tool queries historical transaction data without creating, modifying, deleting, or executing any operations. Even though it belongs to a financial system, reading transaction history does not move money, create obligations, or modify any state. The severity is low because such history queries, while sensitive data-wise, do not expose the AI agent to financial risk through misuse.
From the tool's definition Tool description is 'Get transaction history' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs transaction_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MIDAS Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transaction_history, this is the rule to start with:
transaction_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MIDAS Protocol, apply this rule, and every transaction_history call is checked against it from then on.
Questions about transaction_history
Get transaction history. It is categorised as a Read tool in the MIDAS Protocol MCP Server, which means it retrieves data without modifying state.
transaction_history accepts 2 parameters: limit, offset. The full parameter table on this page comes from the server's own tool schema.
Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for transaction_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 MIDAS Protocol. Nothing to install.
transaction_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 transaction_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 transaction_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.
transaction_history is provided by the MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MIDAS Protocol, and thousands of servers like it.
This server
Across the catalogue