Revoke Voucher
AI agents call revoke_vouchers to permanently remove resources in Zbd — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoke operations on financial instruments like vouchers are irreversible and destructive. Once a voucher is revoked, it cannot be reactivated or recovered. This aligns with the Destructive category as the most applicable classification.
From the tool's definition Tool name 'revoke_vouchers' performs a revoke operation on vouchers, which is irreversible. The sibling tools on this server include 'create_vouchers' and 'create_lightning_charges', indicating this is a financial/payments platform.
Attacks that exploit this kind of access
Revoke Voucher. It is categorised as a Destructive tool in the Zbd MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zbd MCP server in PolicyLayer and add a rule for revoke_vouchers: 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 Zbd. Nothing to install.
revoke_vouchers 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 revoke_vouchers 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 revoke_vouchers. 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.
revoke_vouchers is provided by the Zbd MCP server (zebedeeio/zbd-payments-typescript-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
revoke_vouchers is one line of Zbd's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →