AI agents call balance-history 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 retrieves historical account balance information. 'Get' operations that query data without creating, modifying, or deleting records are classified as Read. There is no state change, financial transaction execution, or destructive action. The low severity reflects that reading historical balance data poses minimal risk—an AI agent cannot misuse this to cause financial harm or data loss.
From the tool's definition Tool name 'balance-history' and description 'Get account balance history over time' indicate retrieval of historical data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access balance-history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Actual, and nothing reaches the server without passing your rules. This is the rule we recommend for balance-history:
{
"version": "1",
"default": "deny",
"tools": {
"balance-history": {}
}
}balance-history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get account balance history over time. 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 balance-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 Actual. Nothing to install.
balance-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 balance-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 balance-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.
balance-history is provided by the Actual MCP server (s-stefanov/actual-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Actual tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
25 Actual tools catalogued and risk-classified — across an index of 42,500+ MCP servers.