create_contract_payment
Create a new payment for a contract
This record as markdown: /tools/adbutler/create-contract-payment.md
What create_contract_payment does on AdButler
AI agents use create_contract_payment to commit financial operations through AdButler, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
note | string | — | Payment note or description |
amount | number | Yes | Amount paid (can be negative for refunds) |
contract_id | number | Yes | Contract ID |
Parameters from the server's own tool schema.
Why create_contract_payment is rated Critical
This tool explicitly creates a financial payment tied to a contract, which constitutes a financial obligation. Misuse could result in unauthorized payments being initiated, making this a critical financial risk.
From the tool's definition "Create a new payment for a contract"
Attacks that exploit this kind of access
The rule that runs create_contract_payment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_contract_payment, this is the rule to start with:
Any call to create_contract_payment is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every create_contract_payment call is checked against it from then on.
Questions about create_contract_payment
Create a new payment for a contract. It is categorised as a Financial tool in the AdButler MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
create_contract_payment accepts 3 parameters: note, amount, contract_id. Required: amount, contract_id. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for create_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.
create_contract_payment is a Financial 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on AdButler, and thousands of servers like it.
Across the catalogue