Get recent transactions for the wallet (limited functionality)
AI agents call get_transaction_history to retrieve information from KaiaFun MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves transaction history data without modifying, executing code, deleting, or moving funds. It is purely informational. While the server offers financial tools (buy_memecoin, sell_memecoin), this specific tool only fetches data. The 'limited functionality' note suggests minimal scope, further supporting low severity.
From the tool's definition Tool name is 'get_transaction_history' and description states it retrieves 'recent transactions for the wallet'. The verb 'get' and passive retrieval of historical data indicate a read-only operation with no side effects.
Attacks that exploit this kind of access
Get recent transactions for the wallet (limited functionality). It is categorised as a Read tool in the KaiaFun MCP MCP Server, which means it retrieves data without modifying state.
Register the KaiaFun MCP server in PolicyLayer and add a rule for get_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 KaiaFun MCP. Nothing to install.
get_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 get_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 get_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.
get_transaction_history is provided by the KaiaFun MCP server (weero-finance/kaiafun-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 →