hives_detach_context_project

hives_detach_context_project (DELETE /v1/hives/context/project) [service status: down]

SERVERGenesis SOURCE@lifesi/genesis-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lifesi-genesis-mcp/hives-detach-context-project.md

WHAT IT DOES

What hives_detach_context_project does on Genesis

AI agents call hives_detach_context_project 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.

RISK

Why hives_detach_context_project is rated Critical

An AI agent that decides to call hives_detach_context_project 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hives_detach_context_project 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_detach_context_project, this is the rule to start with:

hives_detach_context_project Hidden

hives_detach_context_project is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "hives_detach_context_project"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every hives_detach_context_project call is checked against it from then on.

FAQ

Questions about hives_detach_context_project

What does the hives_detach_context_project tool do? +

hives_detach_context_project (DELETE /v1/hives/context/project) [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.

How do I enforce a policy on hives_detach_context_project? +

Register the Genesis MCP server in PolicyLayer and add a rule for hives_detach_context_project: 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.

What risk level is hives_detach_context_project? +

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

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

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

hives_detach_context_project 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.

KEEP EXPLORING

More on Genesis, and thousands of servers like it.

This server

All 252 Genesis tools → Critical-risk tools on this server →

Across the catalogue

clear_project_index on ACE-MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →