AI agents use update_voucher_position to create or update resources in Sevdesk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sevdesk environment.
This tool creates or modifies accounting data (a voucher position) in a reversible manner. It is not Destructive because updates can be reverted. It is not Financial itself—moving money is handled by separate tools like 'book_voucher_payment'—but operates on financial records.
From the tool's definition update_voucher_position performs an update operation on an existing voucher position, modifying reversible financial accounting data.
Attacks that exploit this kind of access
Update an existing voucher position. It is categorised as a Write tool in the Sevdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sevdesk MCP server in PolicyLayer and add a rule for update_voucher_position: 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 Sevdesk. Nothing to install.
update_voucher_position 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 update_voucher_position 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 update_voucher_position. 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.
update_voucher_position is provided by the Sevdesk MCP server (codestra/sevdesk-mcp). 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 →