AI agents call get_voucher 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 tool retrieves a single voucher/receipt record by ID without side effects. It is a simple data query operation that does not create, modify, delete, or execute any external operations. No financial transactions are initiated. This is a straightforward Read category tool with low risk.
From the tool's definition Tool name is 'get_voucher' with description 'Get a specific voucher/receipt by ID from sevdesk'. The verb 'Get' and the absence of any mention of modification, deletion, or execution indicates a read-only retrieval operation.
Attacks that exploit this kind of access
Get a specific voucher/receipt by ID from sevdesk. 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: 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 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 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. 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 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 →