create_signature_request
Create a new signature request for a contract
This record as markdown: /tools/adbutler/create-signature-request.md
What create_signature_request does on AdButler
AI agents use create_signature_request to create or update resources in AdButler, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
contract_id | number | Yes | Contract ID |
Parameters from the server's own tool schema.
Why create_signature_request is rated Medium
This tool creates (writes) a new signature request artifact for a contract. While this initiates a legal process, the action itself is reversible (the request can be cancelled or modified before signing is complete), distinguishing it from Destructive or Financial categories. It modifies system state by adding a new record, making it a Write operation.
From the tool's definition Tool name is 'create_signature_request' and description states 'Create a new signature request for a contract'. The verb 'create' indicates a reversible write operation that generates a new contract signature request in the AdButler system.
Attacks that exploit this kind of access
The rule that runs create_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 create_signature_request, this is the rule to start with:
create_signature_request stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every create_signature_request call is checked against it from then on.
Questions about create_signature_request
Create a new signature request for a contract. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_signature_request accepts 1 parameter: contract_id. Required: 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_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.
create_signature_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.
This server
Across the catalogue