get_signature_request
Get details of a specific signature request
This record as markdown: /tools/adbutler/get-signature-request.md
What get_signature_request does on AdButler
AI agents call get_signature_request 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 |
|---|---|---|---|
id | number | Yes | Signature request ID |
contract_id | number | Yes | Contract ID |
Parameters from the server's own tool schema.
Why get_signature_request is rated Low
This tool retrieves and queries information about a signature request without modifying, executing operations, or causing irreversible changes. It is a straightforward read operation with minimal blast radius if misused by an agent—at worst, it exposes signature request details to which the agent may or may not have authorization, but causes no data modification or financial impact.
From the tool's definition Tool name 'get_signature_request' with description 'Get details of a specific signature request' indicates retrieval of existing data with the verb 'Get'.
Attacks that exploit this kind of access
The rule that runs get_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 get_signature_request, this is the rule to start with:
get_signature_request 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 get_signature_request call is checked against it from then on.
Questions about get_signature_request
Get details of a specific 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 accepts 2 parameters: id, contract_id. Required: 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 get_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.
get_signature_request 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 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. 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 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