Enshrine (finalize) an invoice in sevdesk — prevents further changes
AI agents call enshrine_invoice to permanently remove resources in Sevdesk — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Enshrining an invoice makes it immutable and irreversible — once finalized, the invoice cannot be modified or undone. This permanent lock on data qualifies as a Destructive action due to its irreversible nature, with high severity since it could lock incorrect financial documents permanently.
From the tool's definition 'Enshrine (finalize) an invoice in sevdesk — prevents further changes'
Attacks that exploit this kind of access
Enshrine (finalize) an invoice in sevdesk — prevents further changes. It is categorised as a Destructive tool in the Sevdesk MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sevdesk MCP server in PolicyLayer and add a rule for enshrine_invoice: 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.
enshrine_invoice is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the enshrine_invoice 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 enshrine_invoice. 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.
enshrine_invoice 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 →