AI agents call get_contract_document_file_revision 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 |
|---|---|---|---|
contract_id | number | Yes | Contract ID |
document_id | number | Yes | Document ID |
revision_id | number | Yes | File revision ID |
Parameters from the server's own tool schema.
This tool retrieves a specific historical version of a contract document file. The use of 'get' and 'revision' (implying historical access) confirms it is a read-only operation with no side effects. While contract documents may contain sensitive business information, the tool itself performs only retrieval without the ability to modify, execute actions, or create financial obligations.
From the tool's definition Tool name 'get_contract_document_file_revision' and description 'Get a specific file revision for a contract document' indicate retrieval of existing contract document data without modification or deletion.
Attacks that exploit this kind of access
Get a specific file revision for a contract document. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_contract_document_file_revision accepts 3 parameters: contract_id, document_id, revision_id. Required: contract_id, document_id, revision_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_contract_document_file_revision: 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_contract_document_file_revision 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_contract_document_file_revision 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_contract_document_file_revision. 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_contract_document_file_revision 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 →