AI agents call get_transactions to retrieve information from Actual 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 existing transaction data without creating, modifying, or deleting any information. It has no side effects beyond data retrieval, making it a Read operation with low severity. The blast radius is minimal—an AI agent misusing this tool could only access financial transaction history, not alter it or access sensitive operations. Confidence is high given the clear read-only semantics.
From the tool's definition Tool retrieves recent transactions for a specific account. The verb 'gets' and the read-only nature of retrieving transaction data indicates no modification or deletion of data.
Attacks that exploit this kind of access
Gets recent transactions for a specific account. It is categorised as a Read tool in the Actual MCP Server, which means it retrieves data without modifying state.
Register the Actual MCP server in PolicyLayer and add a rule for get_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 Actual. Nothing to install.
get_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_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_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_transactions is provided by the Actual MCP server (slushpupie/actual-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 →