AI agents call get_signature_request_recipient 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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 performs a read-only query to retrieve information about a signature request recipient. It has no destructive, financial, or execution capabilities—it merely fetches existing data. The blast radius of misuse is minimal, as reading signature request recipient data poses low security risk in an ad management context.
From the tool's definition Tool name 'get_signature_request_recipient' and description 'Get a specific recipient for a signature request' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get a specific recipient for a signature request. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_signature_request_recipient accepts 3 parameters: 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 get_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.
get_signature_request_recipient 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 get_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 get_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.
get_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 →