Delete a contract from the project
AI agents call delete-contract to permanently remove resources in Openfort MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a contract resource, which cannot be undone. Deletion is an irreversible destructive action. The severity is high because deleting a contract could break dependent configurations, applications, or wallet operations that reference it, but the blast radius is scoped to a single contract rather than an entire system or financial accounts.
From the tool's definition delete-contract with description 'Delete a contract from the project' — the word 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a contract from the project. It is categorised as a Destructive tool in the Openfort MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Openfort MCP Server MCP server in PolicyLayer and add a rule for delete-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 Openfort MCP Server. Nothing to install.
delete-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 delete-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 delete-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.
delete-contract is provided by the Openfort MCP Server MCP server (openfort-xyz/-deprecated-mcp). 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 →