record_income
AI agents use record_income to create or update resources in Finance App — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Finance App environment.
The name 'record_income' strongly implies creating a new financial transaction entry (income record) in the accounting system. This is a Write operation — it creates data in a double-entry accounting ledger. While it touches financial data, it does not directly move money or commit financial obligations externally; it records an internal accounting entry.
From the tool's definition Tool name: 'record_income'; server description mentions managing accounts, transactions, budgets via a double-entry accounting service.
Attacks that exploit this kind of access
record_income. It is categorised as a Write tool in the Finance App MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Finance App MCP server in PolicyLayer and add a rule for record_income: 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 Finance App. Nothing to install.
record_income 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 record_income 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 record_income. 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.
record_income is provided by the Finance App MCP server (youssefaltai/finance-app). 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 →