hives_marketplace_uninstall
Persist uninstall intent before stopping every retained workload. (DELETE /v1/hives/projects/{project_id}/marketplace/installed/{installation_id}) [service status: down]
This record as markdown: /tools/lifesi-genesis-mcp/hives-marketplace-uninstall.md
What hives_marketplace_uninstall does on Genesis
AI agents call hives_marketplace_uninstall to permanently remove resources in Genesis, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes | Verified owned Hives project |
installation_id | string | Yes | Owned persisted installation |
Parameters from the server's own tool schema.
Why hives_marketplace_uninstall is rated Critical
An AI agent that decides to call hives_marketplace_uninstall doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Genesis is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs hives_marketplace_uninstall safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hives_marketplace_uninstall, this is the rule to start with:
hives_marketplace_uninstall 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 Genesis, apply this rule, and every hives_marketplace_uninstall call is checked against it from then on.
Questions about hives_marketplace_uninstall
Persist uninstall intent before stopping every retained workload. (DELETE /v1/hives/projects/{project_id}/marketplace/installed/{installation_id}) [service status: down]. It is categorised as a Destructive tool in the Genesis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
hives_marketplace_uninstall accepts 2 parameters: project_id, installation_id. Required: project_id, installation_id. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for hives_marketplace_uninstall: 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 Genesis. Nothing to install.
hives_marketplace_uninstall 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 hives_marketplace_uninstall 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 hives_marketplace_uninstall. 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.
hives_marketplace_uninstall is provided by the Genesis MCP server (@lifesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
Across the catalogue