list_signature_request_recipients

List all recipients for a signature request

Server AdButler adbutler/mcp-server
Category Read
Risk class Low
Parameters 22 required

What list_signature_request_recipients does on AdButler

AI agents call list_signature_request_recipients to retrieve information from AdButler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
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 needs a policy

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.

Questions about list_signature_request_recipients

What does the list_signature_request_recipients tool do? +

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.

What parameters does list_signature_request_recipients accept? +

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.

How do I enforce a policy on list_signature_request_recipients? +

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.

What risk level is list_signature_request_recipients? +

list_signature_request_recipients is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_signature_request_recipients? +

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.

How do I block list_signature_request_recipients completely? +

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.

What MCP server provides list_signature_request_recipients? +

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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.