AI agents call get_voucher_position to retrieve information from Sevdesk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval operation. It queries an existing voucher position from the sevdesk accounting system without side effects. Misuse by an AI agent would only expose existing accounting data, not create financial obligations or modify records. This aligns with the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).'
From the tool's definition Tool name 'get_voucher_position' and description 'Get a specific voucher position by ID' indicate retrieval of a single voucher position record by identifier. No modifications, deletions, or external operations are triggered.
Attacks that exploit this kind of access
Get a specific voucher position by ID. It is categorised as a Read tool in the Sevdesk MCP Server, which means it retrieves data without modifying state.
Register the Sevdesk MCP server in PolicyLayer and add a rule for get_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.
get_voucher_position is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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 →