list_signature_request_recipients
List all recipients for a signature request
This record as markdown: /tools/adbutler/list-signature-request-recipients.md
What list_signature_request_recipients does on AdButler
AI agents call list_signature_request_recipients to retrieve information from AdButler without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| 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 list_signature_request_recipients is rated Low
This tool queries and returns signature request recipient data without making any changes, triggering actions, or deleting information. It is a straightforward read/list operation, typical of informational access to advertising campaign or contract management systems.
From the tool's definition Tool name and description indicate 'List all recipients' – a retrieval operation with no modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs list_signature_request_recipients 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 list_signature_request_recipients, this is the rule to start with:
list_signature_request_recipients is read-only, so it stays allowed. 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 list_signature_request_recipients call is checked against it from then on.
Questions about list_signature_request_recipients
List all recipients for a signature request. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
list_signature_request_recipients 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 list_signature_request_recipients: 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.
list_signature_request_recipients is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_signature_request_recipients 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 list_signature_request_recipients. 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.
list_signature_request_recipients 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