This record as markdown: /tools/adbutler/cancel-signature-request.md
What cancel_signature_request does on AdButler
AI agents call cancel_signature_request 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
request_id | number | Yes | Signature request ID |
contract_id | number | Yes | Contract ID |
Parameters from the server's own tool schema.
Why cancel_signature_request is rated Critical
Cancelling a signature request cannot be undone; once cancelled, the signing parties would need a new request to be initiated. This is an irreversible operation, placing it in the Destructive category. The blast radius is high because it could disrupt legal or contractual workflows.
From the tool's definition 'cancel_signature_request' — cancelling a signature request is an irreversible action that terminates a pending agreement or contract signing workflow
Attacks that exploit this kind of access
The rule that runs cancel_signature_request 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 cancel_signature_request, this is the rule to start with:
cancel_signature_request is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every cancel_signature_request call is checked against it from then on.
Questions about cancel_signature_request
Cancel a signature request. 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.
cancel_signature_request accepts 2 parameters: request_id, contract_id. Required: request_id, 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 cancel_signature_request: 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.
cancel_signature_request 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 cancel_signature_request 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 cancel_signature_request. 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.
cancel_signature_request 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