Critical Risk →

delete_payment

Delete a payment

Part of the Bexio server.

delete_payment can permanently delete data in Bexio, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE BEXIO →

Free to start. No card required.

AI agents may call delete_payment to permanently remove or destroy resources in Bexio. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call delete_payment in a loop, permanently destroying resources in Bexio. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_payment"
  ]
}

See the full Bexio policy for all 276 tools.

Get this rule live on your own Bexio server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY BEXIO →

View all 276 tools →

These attack patterns abuse exactly the kind of access delete_payment gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so delete_payment only ever does what you allow.

SECURE BEXIO →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the delete_payment tool do? +

Delete a payment. It is categorised as a Destructive tool in the Bexio MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_payment? +

Register the Bexio MCP server in PolicyLayer and add a rule for delete_payment: 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 Bexio. Nothing to install.

What risk level is delete_payment? +

delete_payment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_payment? +

Yes. Add a rate_limit block to the delete_payment 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.

How do I block delete_payment completely? +

Set action: deny in the PolicyLayer policy for delete_payment. 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.

What MCP server provides delete_payment? +

delete_payment is provided by the Bexio MCP server (@promptpartner/bexio-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bexio tool call.

Deterministic rules across all 276 Bexio tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.