Skip to main content
Every event arrives in the same envelope. This page describes data for each type. The examples are spread over several lines to make them readable. The Cimento SDKs have a type for each event’s data: see the payload types in the Go reference, or narrow on event.type in TypeScript. Agent Hub events name people and things by id. They never include a prompt, a command, file contents or anything else an AI agent’s session contained. The one piece of generated text is a finding’s title.

Findings

A finding is something a rule matched. Treat ruleId as text that can take new values: Cimento adds rules over time.
agent_hub.finding.created is sent only for findings whose rule nudged or blocked the person. A finding from a rule set to watch or fix is not announced, but its later events are still sent. So you can receive a decided, decision_cleared or closed event for a findingId you have never seen. Handle those without assuming a created came first.

agent_hub.finding.created

A rule that nudges or blocks matched something an AI agent did.
This event arrives a few minutes after the finding, because Cimento waits for the finding’s title to be written. If the title isn’t ready in time, title is the rule’s name.

agent_hub.finding.decided

An admin recorded a decision on a finding. More decisions can be added, so handle a value you don’t recognize.

agent_hub.finding.decision_cleared

An admin cleared the decision on a finding, reopening it. data has the same fields as agent_hub.finding.decided, and decision is null.

agent_hub.finding.closed

The condition behind an ongoing finding cleared. This applies to findings whose kind is exposure: the device reported the control back in place, or the rule was turned off.

Rules and settings

agent_hub.rule.updated

An admin changed how a rule responds. Saving a rule without changing its response sends nothing.
Turning a rule off closes its open findings, which sends agent_hub.finding.closed for each.

agent_hub.settings.updated

An admin changed Agent Hub settings. The event names the settings that changed, never their values. Saving without changing anything sends nothing.

MCP servers

Both events share the same data. They say which server gained or lost an approval, not who it was approved for. A server can be approved for everyone, a group, a department or one person, so you can receive more than one approved event for the same server. Approving or revoking several servers at once sends one event for each server. Declining a server sends nothing.

agent_hub.mcp_server.approved

An admin approved an MCP server.

agent_hub.mcp_server.revoked

An admin revoked an MCP server’s approval.

Attack simulations

agent_hub.simulation.requested

An admin requested an attack simulation.

agent_hub.simulation.completed

An attack simulation run finished. The event carries counts only: nothing about which attack landed on which agent.