runner_getJobEvents

Read an ordered page of Runner job events (GET /v1/runner/jobs/{jobId}/events) [service status: not_deployed]

SERVERGenesis SOURCE@lifesi/genesis-mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lifesi-genesis-mcp/runner-getjobevents.md

WHAT IT DOES

What runner_getJobEvents does on Genesis

AI agents call runner_getJobEvents to retrieve information from Genesis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`jobId`	object	Yes
`afterSeq`	integer	—	Exclusive event cursor. Use nextAfterSeq for the next page.

Parameters from the server's own tool schema.

RISK

Why runner_getJobEvents is rated Low

Even though runner_getJobEvents only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

runner_getJobEvents Allowed

runner_getJobEvents is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "runner_getJobEvents": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about runner_getJobEvents

What does the runner_getJobEvents tool do? +

Read an ordered page of Runner job events (GET /v1/runner/jobs/{jobId}/events) [service status: not_deployed]. It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.

What parameters does runner_getJobEvents accept? +

runner_getJobEvents accepts 2 parameters: jobId, afterSeq. Required: jobId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on runner_getJobEvents? +

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

runner_getJobEvents is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit runner_getJobEvents? +

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

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

runner_getJobEvents 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

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →