This record as markdown: /tools/adbutler/resend-signature-request.md
What resend_signature_request does on AdButler
AI agents use resend_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 |
|---|---|---|---|
request_id | number | Yes | Signature request ID |
contract_id | number | Yes | Contract ID |
Parameters from the server's own tool schema.
Why resend_signature_request is rated Medium
Resending a signature request triggers an external communication/notification action (sending an email or similar request to a recipient). This is a Write/Execute-adjacent action — it creates a side effect by re-dispatching a request — but it does not irreversibly destroy data or move money.
From the tool's definition Resend a signature request
Attacks that exploit this kind of access
The rule that runs resend_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 resend_signature_request, this is the rule to start with:
resend_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 resend_signature_request call is checked against it from then on.
Questions about resend_signature_request
Resend 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.
resend_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 resend_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.
resend_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 resend_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 resend_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.
resend_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