Create an income transaction in Wave from payment/receipt data. Customer is optional - income can be created without customer association and customers can be added later.
AI agents use create_income_from_payment to create or update resources in Wave Accounting MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wave Accounting MCP Server environment.
This tool creates new financial transaction records in Wave Accounting. While the creation itself is reversible (Write rather than Destructive), it directly modifies the user's accounting data by adding income transactions.
From the tool's definition Tool description states it 'Create[s] an income transaction in Wave' - this is a create operation that modifies financial data in the accounting system.
Documented attack patterns abuse exactly the kind of access create_income_from_payment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wave Accounting MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_income_from_payment:
{
"version": "1",
"default": "deny",
"tools": {
"create_income_from_payment": {
"limits": [
{
"counter": "create_income_from_payment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_income_from_payment 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.
Create an income transaction in Wave from payment/receipt data. Customer is optional - income can be created without customer association and customers can be added later. It is categorised as a Write tool in the Wave Accounting MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wave Accounting MCP Server MCP server in PolicyLayer and add a rule for create_income_from_payment: 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 Wave Accounting MCP Server. Nothing to install.
create_income_from_payment 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 create_income_from_payment 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 create_income_from_payment. 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.
create_income_from_payment is provided by the Wave Accounting MCP Server MCP server (vinnividivicci/wave_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wave Accounting MCP Server, 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.
9 Wave Accounting MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.