Emit append-only run telemetry for OrgX control-plane reporting. USE WHEN: agent is executing and needs to report progress. NEXT: Continue work; emit again at each phase change. DO NOT USE: for entity status changes — use entity_action instead. Setting phase="completed" records telemetry only and...
AI agents invoke orgx_emit_activity to trigger actions in OrgX. 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 |
|---|---|---|---|
level | string | — | Optional severity level for the activity event |
phase | string | — | Optional reporting phase for the activity event |
run_id | string | — | Existing run UUID |
message | string | — | Human-readable activity update |
runtime | object | — | Runtime provenance used by /live to bucket cloud, local, Anthropic, managed, and OpenClaw chokepoints |
_context | object | — | Client context for conversation tracking (strongly recommended for cross-client continuity) |
metadata | object | — | Optional structured metadata to attach to the activity event |
next_step | string | — | Optional next step to surface after this activity event |
chokepoint | object | — | Durable blocker/stall/error/approval to surface in /live when execution cannot proceed |
progress_pct | number | — | Optional progress percentage associated with this activity |
initiative_id | string | — | Initiative UUID |
source_client | string | — | Required when run_id is not provided |
Parameters from the server's own tool schema.
orgx_emit_activity 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 signalsHigh parameter count (41 properties)
Documented attack patterns abuse exactly the kind of access orgx_emit_activity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OrgX, and nothing reaches the server without passing your rules. This is the rule we recommend for orgx_emit_activity:
{
"version": "1",
"default": "deny",
"tools": {
"orgx_emit_activity": {
"limits": [
{
"counter": "orgx_emit_activity_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}orgx_emit_activity 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.
Free to start. No card required.
Emit append-only run telemetry for OrgX control-plane reporting. USE WHEN: agent is executing and needs to report progress. NEXT: Continue work; emit again at each phase change. DO NOT USE: for entity status changes — use entity_action instead. Setting phase="completed" records telemetry only and does not mark tasks, workstreams, or initiatives complete. It is categorised as a Execute tool in the OrgX MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
orgx_emit_activity accepts 12 parameters: level, phase, run_id, message, runtime, _context, metadata, next_step, chokepoint, progress_pct, initiative_id, source_client. The full parameter table on this page comes from the server's own tool schema.
Register the OrgX MCP server in PolicyLayer and add a rule for orgx_emit_activity: 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 OrgX. Nothing to install.
orgx_emit_activity 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 orgx_emit_activity 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 orgx_emit_activity. 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.
orgx_emit_activity is provided by the OrgX MCP server (useorgx/orgx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 OrgX tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 OrgX tools catalogued and risk-classified — across an index of 42,500+ MCP servers.