cancel_signature_request

Cancel a signature request

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

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.

ParameterTypeRequiredDescription
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 needs a policy

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

Questions about cancel_signature_request

What does the cancel_signature_request tool do? +

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.

What parameters does cancel_signature_request accept? +

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.

How do I enforce a policy on cancel_signature_request? +

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.

What risk level is cancel_signature_request? +

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.

Can I rate-limit cancel_signature_request? +

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.

How do I block cancel_signature_request completely? +

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.

What MCP server provides cancel_signature_request? +

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.

// 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.