list_contract_document_file_revisions
List file revisions for a contract document
This record as markdown: /tools/adbutler/list-contract-document-file-revisions.md
What list_contract_document_file_revisions does on AdButler
AI agents call list_contract_document_file_revisions 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 |
|---|---|---|---|
contract_id | number | Yes | Contract ID |
document_id | number | Yes | Document ID |
Parameters from the server's own tool schema.
Why list_contract_document_file_revisions is rated Low
This tool retrieves historical revision metadata for contract documents. It queries existing data without creating, modifying, deleting, or executing any operations. The action is read-only and poses minimal risk even if invoked by an AI agent, as it only exposes audit/version history information.
From the tool's definition Tool name contains 'list' and description states 'List file revisions for a contract document' — a pure data retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs list_contract_document_file_revisions 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 list_contract_document_file_revisions, this is the rule to start with:
list_contract_document_file_revisions 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 list_contract_document_file_revisions call is checked against it from then on.
Questions about list_contract_document_file_revisions
List file revisions for a contract document. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
list_contract_document_file_revisions accepts 2 parameters: contract_id, document_id. Required: contract_id, document_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_contract_document_file_revisions: 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_contract_document_file_revisions 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_contract_document_file_revisions 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_contract_document_file_revisions. 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_contract_document_file_revisions 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