New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

opportunities_delete_opportunity

Delete Opportunity

SERVERGhl SOURCE@aiwerk/mcp-server-ghl
Critical RISK CLASS
Category Destructive
Parameters 11 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/opportunities-delete-opportunity.md

What opportunities_delete_opportunity does on Ghl

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

ParameterTypeRequiredDescription
id string Yes Opportunity Id

Parameters from the server's own tool schema.

Why opportunities_delete_opportunity is rated Critical

An AI agent that decides to call opportunities_delete_opportunity doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ghl is gone. There is no undo for destructive operations.

Questions about opportunities_delete_opportunity

What does the opportunities_delete_opportunity tool do? +

Delete Opportunity. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does opportunities_delete_opportunity accept? +

opportunities_delete_opportunity accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on opportunities_delete_opportunity? +

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

What risk level is opportunities_delete_opportunity? +

opportunities_delete_opportunity 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 opportunities_delete_opportunity? +

Yes. Add a rate_limit block to the opportunities_delete_opportunity 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 opportunities_delete_opportunity completely? +

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

opportunities_delete_opportunity is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Ghl, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ghl's. Pull the full record:

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.