Returns wallet history - operations recorded on the wallet
AI agents call account-history to retrieve information from Walutomat MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely queries and retrieves historical data about wallet operations. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations.
From the tool's definition Tool returns wallet history and operations recorded on the wallet; it retrieves historical data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Returns wallet history - operations recorded on the wallet. It is categorised as a Read tool in the Walutomat MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Walutomat MCP Server MCP server in PolicyLayer and add a rule for account-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 Walutomat MCP Server. Nothing to install.
account-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 account-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 account-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.
account-history is provided by the Walutomat MCP Server MCP server (jpospychala/walutomat-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 →