AI agents use update_signature_request_recipient 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 |
|---|---|---|---|
name | string | — | Recipient name |
email | string | — | Recipient email |
request_id | number | Yes | Signature request ID |
contract_id | number | Yes | Contract ID |
recipient_id | number | Yes | Recipient ID |
Parameters from the server's own tool schema.
This tool modifies (updates) recipient information for a signature request, which is a reversible write operation. It does not delete data (would be Destructive), does not execute code or external operations (would be Execute), and does not involve financial transactions (would be Financial).
From the tool's definition Tool name contains 'update' and description states 'Update a recipient for a signature request', indicating modification of existing data related to signature request recipients.
Attacks that exploit this kind of access
Update a recipient for a signature request. 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.
update_signature_request_recipient accepts 5 parameters: name, email, request_id, contract_id, recipient_id. Required: request_id, contract_id, recipient_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 update_signature_request_recipient: 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.
update_signature_request_recipient 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 update_signature_request_recipient 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 update_signature_request_recipient. 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.
update_signature_request_recipient 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.
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 →