beancount_submit_transaction
AI agents use beancount_submit_transaction to create or update resources in Beancount — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Beancount environment.
This tool creates or modifies financial transaction records in a Beancount ledger. While not immediately moving money (which would be Financial category), it writes irreversible or difficult-to-audit changes to financial records. The high severity reflects that an AI agent could submit unauthorized or erroneous transactions, affecting financial accounting integrity.
From the tool's definition Tool name 'beancount_submit_transaction' combined with server description stating 'submit transaction' indicates creation/modification of financial ledger entries. No description provided for the tool itself, limiting confidence slightly.
Documented attack patterns abuse exactly the kind of access beancount_submit_transaction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Beancount, and nothing reaches the server without passing your rules. This is the rule we recommend for beancount_submit_transaction:
{
"version": "1",
"default": "deny",
"tools": {
"beancount_submit_transaction": {
"limits": [
{
"counter": "beancount_submit_transaction_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}beancount_submit_transaction stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
beancount_submit_transaction. It is categorised as a Write tool in the Beancount MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Beancount MCP server in PolicyLayer and add a rule for beancount_submit_transaction: 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 Beancount. Nothing to install.
beancount_submit_transaction is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the beancount_submit_transaction 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 beancount_submit_transaction. 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.
beancount_submit_transaction is provided by the Beancount MCP server (stdioa/beancount-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Beancount, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Beancount tools catalogued and risk-classified — across an index of 43,000+ MCP servers.