hives_resume_cron

Resume a cron job (POST /v1/hives/projects/{project_id}/cron/{cron_id}/resume) [service status: down]

SERVERGenesis SOURCE@lifesi/genesis-mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lifesi-genesis-mcp/hives-resume-cron.md

WHAT IT DOES

What hives_resume_cron does on Genesis

AI agents use hives_resume_cron to create or update resources in Genesis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Genesis environment.

Parameter	Type	Required	Description
`cron_id`	string	Yes	Cron job ID
`project_id`	string	Yes	Project ID

Parameters from the server's own tool schema.

RISK

Why hives_resume_cron is rated Medium

An AI agent can call hives_resume_cron faster than any human can review: one bad instruction and it creates or modifies resources in Genesis by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hives_resume_cron Rate-limited

hives_resume_cron stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hives_resume_cron": {
      "limits": [
        {
          "counter": "hives_resume_cron_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about hives_resume_cron

What does the hives_resume_cron tool do? +

Resume a cron job (POST /v1/hives/projects/{project_id}/cron/{cron_id}/resume) [service status: down]. It is categorised as a Write tool in the Genesis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does hives_resume_cron accept? +

hives_resume_cron accepts 2 parameters: cron_id, project_id. Required: cron_id, project_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hives_resume_cron? +

Register the Genesis MCP server in PolicyLayer and add a rule for hives_resume_cron: 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_resume_cron? +

hives_resume_cron is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hives_resume_cron? +

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

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

hives_resume_cron 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 →

Across the catalogue

resume_renders on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →