ColomboAIDOCS
API ReferenceCookbook
Docs/MC-1 Security/Security source connectors
PublishedGuidanceLAST REVIEWED · 18 NOV 2026

Security source connectors

Authenticate one explicit tenant/project/agent source and deliver bounded, retry-safe telemetry.

Runtime scope

Create the binding

A current signed-in owner or administrator selects an active registered agent, an approved AATS mapping and a dedicated non-executing Trust target. The target scope includes security_workspace_id equal to this project ID; allowed_actions is an empty list.

The mc1_event_push_v1 source token is shown once, expires within24hours and is stored only as a digest. It cannot query incidents, approve a response or dispatch a command. Keep it in the approved source secret store; revoke it if delivery setup is abandoned.

Normalized events

  • Schema version1; exact registered agent binding.
  • source_event_id and correlation_id are bounded identifiers.
  • occurred_at is the original Unix-millisecond occurrence time, not ingestion time; permitted skew is at most one minute into the future and30days into the past.
  • Categories: agent.policy, agent.identity, agent.mission, mcp.activity and application.auth.
  • Outcomes: allowed, denied, error and unknown. Severity and numeric source confidence remain source reports.
  • Optional asset, identity and mission identifiers; no arbitrary raw log field, URL, script or instruction is accepted.

Retry and capacity

The body limit is16KiB. Identical tenant/connector/source-event IDs return the durable original receipt; different normalized content with that ID returns409 and cannot commit a false incident. Acknowledgement follows transactional commit.

This preview admits120 new-event attempts per project per minute, at most10000 retained telemetry records per project and20 active connectors. Capacity exhaustion returns an error rather than silently dropping acknowledged evidence. The source retention interval is explicitly selected from one hour through30days; production retention and erasure operations must be qualified separately.

Repository JavaScript client

The module is included in the reviewed source tree; this is not a claim that a new NPM package has been published. Supply owned source and target IDs from the approved deployment.

import { SecurityClient } from "./sdk/security-client.mjs";
const source = new SecurityClient({
  origin: process.env.MC1_SECURITY_URL,
  token: process.env.MC1_SECURITY_CONNECTOR_TOKEN,
});
await source.ingest(process.env.MC1_SECURITY_CONNECTOR_ID, {
  schema_version: 1, source_event_id: process.env.SOURCE_EVENT_ID,
  agent_id: process.env.REGISTERED_AGENT_ID, occurred_at: Date.now(),
  category: "agent.policy", action: "tool.execute", outcome: "denied",
  severity: "high", source_confidence: 0.8,
  correlation_id: process.env.CORRELATION_ID,
});
End of guide
Was this page helpful?
Security source connectors | MC-1 Docs