delete_contract_payment

Delete a contract payment

Server AdButler adbutler/mcp-server
Category Destructive
Risk class Critical
Parameters 22 required

What delete_contract_payment does on AdButler

AI agents call delete_contract_payment to permanently remove resources in AdButler — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
id number Yes Payment ID
contract_id number Yes Contract ID

Parameters from the server's own tool schema.

Why delete_contract_payment needs a policy

Deleting contract payments is an irreversible action that destroys financial records and transaction history. This could corrupt billing records, accounting systems, and financial reporting. Even though no funds are directly moved, the destruction of payment records constitutes a critical destructive operation in a financial management context.

From the tool's definition Tool name contains 'delete' and description states 'Delete a contract payment' — a payment record in a financial system cannot be recovered once deleted.

Questions about delete_contract_payment

What does the delete_contract_payment tool do? +

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

What parameters does delete_contract_payment accept? +

delete_contract_payment accepts 2 parameters: id, contract_id. Required: id, contract_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on delete_contract_payment? +

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

What risk level is delete_contract_payment? +

delete_contract_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_contract_payment? +

Yes. Add a rate_limit block to the delete_contract_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_contract_payment completely? +

Set action: deny in the PolicyLayer policy for delete_contract_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_contract_payment? +

delete_contract_payment is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.