This record as markdown: /tools/aiwerk-mcp-server-ghl/marketplace-uninstall-application.md
What marketplace_uninstall_application does on Ghl
AI agents call marketplace_uninstall_application 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
appId | string | Yes | The application id which is to be uninstalled. |
reason | string | — | The reason for uninstalling the application. Reason is required if you are uninstalling the application as a developer. |
companyId | string | — | The company id from which the application is to be uninstalled. If you pass agency token, then companyId is required. It will uninstall application from agency |
locationId | string | — | The location id from which the application is to be uninstalled. If you pass location token, then locationId is required. It will uninstall application from tha |
Parameters from the server's own tool schema.
Why marketplace_uninstall_application is rated Critical
An AI agent that decides to call marketplace_uninstall_application 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.
Attacks that exploit this kind of access
The rule that runs marketplace_uninstall_application safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For marketplace_uninstall_application, this is the rule to start with:
marketplace_uninstall_application 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 Ghl, apply this rule, and every marketplace_uninstall_application call is checked against it from then on.
Questions about marketplace_uninstall_application
Uninstall an application. 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.
marketplace_uninstall_application accepts 4 parameters: appId, reason, companyId, locationId. Required: appId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for marketplace_uninstall_application: 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.
marketplace_uninstall_application 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 marketplace_uninstall_application 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 marketplace_uninstall_application. 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.
marketplace_uninstall_application 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.
Across the catalogue