AI agents call list_signature_requests 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 |
|---|---|---|---|
limit | number | — | Max results to return (default 100, max 100) |
offset | number | — | Pagination offset |
contract_id | number | Yes | Contract ID |
Parameters from the server's own tool schema.
This tool retrieves and displays signature requests without creating, modifying, deleting, or executing any operations. It is purely informational, fitting the Read category with low severity since the blast radius of misuse (exposing contract signature request metadata) is limited compared to destructive or financial operations.
From the tool's definition Tool name is 'list_signature_requests' and description states 'List all signature requests for a contract' — the verb 'list' and 'all' indicate retrieval/querying of existing data with no modification or side effects.
Attacks that exploit this kind of access
List all signature requests for a contract. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
list_signature_requests accepts 3 parameters: limit, offset, contract_id. Required: 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_requests: 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_requests 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_requests 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_requests. 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_requests 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 →