insert_transaction · MCP Beancount Tool MCP: Risk & Policy

WHAT IT DOES

What insert_transaction does on MCP Beancount Tool

AI agents use insert_transaction to create or update resources in MCP Beancount Tool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Beancount Tool environment.

WHY IT NEEDS A POLICY

Why insert_transaction needs a policy

This tool creates new transactions in an accounting ledger, which is reversible via the sibling remove_transaction tool. While it affects financial records, it does not move money, create financial obligations, or irreversibly delete data—therefore Write rather than Financial or Destructive.

From the tool's definition Tool explicitly states it 'Insert[s] a balanced transaction' which creates new accounting entries in the ledger. The dry-run capability confirms this is a write operation that modifies financial records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insert_transaction Rate-limited

insert_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "insert_transaction": {
      "limits": [
        {
          "counter": "insert_transaction_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Beancount Tool, so you can run agents against it safely.

FAQ

Questions about insert_transaction

What does the insert_transaction tool do? +

Insert a balanced transaction; supports dry-run preview. Provide postings with amounts that sum to zero across currencies. It is categorised as a Write tool in the MCP Beancount Tool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on insert_transaction? +

Register the MCP Beancount Tool MCP server in PolicyLayer and add a rule for insert_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 MCP Beancount Tool. Nothing to install.

What risk level is insert_transaction? +

insert_transaction is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit insert_transaction? +

Yes. Add a rate_limit block to the insert_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.

How do I block insert_transaction completely? +

Set action: deny in the PolicyLayer policy for insert_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.

What MCP server provides insert_transaction? +

insert_transaction is provided by the MCP Beancount Tool MCP server (onesvat/mcp-beancount). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.