close_lease_orchestrated

Orchestrate closing a lease via @manifest-network/manifest-agent-core.

Server Manifest MCP manifest-network/manifest-mcp-mono
Category Destructive
Risk class Critical
Parameters 00 required

What close_lease_orchestrated does on Manifest MCP

AI agents call close_lease_orchestrated to permanently remove resources in Manifest MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why close_lease_orchestrated needs a policy

Closing a lease on a blockchain/Cosmos SDK environment is an irreversible action: once the lease is closed, the associated deployment is terminated and resources are released. This cannot be undone. The sibling tool 'close_lease' confirms this pattern. The 'orchestrated' variant automates the process, potentially increasing blast radius if misused by an AI agent.

From the tool's definition 'close_lease' and 'Orchestrate closing a lease' — closing a lease is an irreversible on-chain operation that terminates a deployment lease, which cannot be undone once committed to the blockchain.

Questions about close_lease_orchestrated

What does the close_lease_orchestrated tool do? +

Orchestrate closing a lease via @manifest-network/manifest-agent-core. It is categorised as a Destructive tool in the Manifest MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on close_lease_orchestrated? +

Register the Manifest MCP server in PolicyLayer and add a rule for close_lease_orchestrated: 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 Manifest MCP. Nothing to install.

What risk level is close_lease_orchestrated? +

close_lease_orchestrated is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit close_lease_orchestrated? +

Yes. Add a rate_limit block to the close_lease_orchestrated 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.

How do I block close_lease_orchestrated completely? +

Set action: deny in the PolicyLayer policy for close_lease_orchestrated. 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.

What MCP server provides close_lease_orchestrated? +

close_lease_orchestrated is provided by the Manifest MCP server (manifest-network/manifest-mcp-mono). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.