archive_contract
Archive a contract (soft-delete, can be restored later)
This record as markdown: /tools/adbutler/archive-contract.md
What archive_contract does on AdButler
AI agents call archive_contract to permanently remove resources in AdButler, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Contract ID |
Parameters from the server's own tool schema.
Why archive_contract is rated Critical
Archiving is a soft-delete operation that removes the contract from active use. While described as restorable, it is a destructive-category action because it deactivates/hides the record similarly to deletion. The 'can be restored later' caveat lowers severity slightly, but the primary effect is disabling an active contract, which could disrupt ongoing advertising obligations.
From the tool's definition Archive a contract (soft-delete, can be restored later)
Attacks that exploit this kind of access
The rule that runs archive_contract 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 archive_contract, this is the rule to start with:
archive_contract is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every archive_contract call is checked against it from then on.
Questions about archive_contract
Archive a contract (soft-delete, can be restored later). It is categorised as a Destructive tool in the AdButler MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
archive_contract accepts 1 parameter: id. Required: 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 archive_contract: 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.
archive_contract is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the archive_contract 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 archive_contract. 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.
archive_contract 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.
Across the catalogue