update_signature_request_recipient

Update a recipient for a signature request

SERVERAdButler SOURCEadbutler/mcp-server

Medium RISK CLASS

Category Write

Parameters 53 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adbutler/update-signature-request-recipient.md

WHAT IT DOES

What update_signature_request_recipient does on AdButler

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.

RISK

Why update_signature_request_recipient is rated Medium

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

RECOMMENDED RULE

The rule that runs update_signature_request_recipient 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 update_signature_request_recipient, this is the rule to start with:

update_signature_request_recipient Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_signature_request_recipient": {
      "limits": [
        {
          "counter": "update_signature_request_recipient_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every update_signature_request_recipient call is checked against it from then on.

FAQ

Questions about update_signature_request_recipient

What does the update_signature_request_recipient tool do? +

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.

What parameters does update_signature_request_recipient accept? +

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.

How do I enforce a policy on update_signature_request_recipient? +

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.

What risk level is update_signature_request_recipient? +

update_signature_request_recipient is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_signature_request_recipient? +

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.

How do I block update_signature_request_recipient completely? +

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.

What MCP server provides update_signature_request_recipient? +

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.

KEEP EXPLORING

More on AdButler, and thousands of servers like it.

This server

All 622 AdButler tools →

Across the catalogue

http_request on 0sec →aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →