hives_invoke_deployment
Invoke a real running owned deployment and return the raw guest HTTP response (POST /v1/hives/projects/{project_id}/deployments/{deployment_id}/invoke) [service status: down]
This record as markdown: /tools/lifesi-genesis-mcp/hives-invoke-deployment.md
What hives_invoke_deployment does on Genesis
AI agents invoke hives_invoke_deployment to trigger actions in Genesis. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | Yes | Exact guest request. Decoded body plus header bytes and serialized guest stdin envelope each have a 10 MiB cap; encoded JSON transport is capped at 16 MiB. body |
project_id | string | Yes | |
deployment_id | string | Yes |
Parameters from the server's own tool schema.
Why hives_invoke_deployment is rated High
hives_invoke_deployment triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts file system path (body.path) · Accepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs hives_invoke_deployment 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_invoke_deployment, this is the rule to start with:
hives_invoke_deployment stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every hives_invoke_deployment call is checked against it from then on.
Questions about hives_invoke_deployment
Invoke a real running owned deployment and return the raw guest HTTP response (POST /v1/hives/projects/{project_id}/deployments/{deployment_id}/invoke) [service status: down]. It is categorised as a Execute tool in the Genesis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
hives_invoke_deployment accepts 3 parameters: body, project_id, deployment_id. Required: body, project_id, deployment_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_invoke_deployment: 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_invoke_deployment is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hives_invoke_deployment 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_invoke_deployment. 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_invoke_deployment 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