Submit a durable receipt (proof, outcome, quality, attribution, or learning) anchored to an OrgX entity or artifact. Required: receipt_type + summary. Strongly recommended: one anchor (entity_type+entity_id OR artifact_id), artifact_type, business_outcome, agent_type, AND at least one verifiable ...
AI agents use orgx_submit_receipt to create or update resources in OrgX — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OrgX environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
summary | string | — | One-sentence human-readable description of what the receipt proves (e.g. "Merged PR #142 unblocking the auth refactor"). |
_context | object | — | Client context for conversation tracking (strongly recommended for cross-client continuity) |
evidence | object | — | Structured evidence payload. Recognized shapes: { prs: string[] }, { deploys: string[] }, { test_runs: string[] }, { metrics: { name, value, unit? }[] }, { link |
entity_id | string | — | Related entity UUID. Required when entity_type is provided. |
agent_type | string | — | Agent/domain that produced the receipt, such as engineering, sales, product, design, operations, marketing, or orchestrator. |
model_tier | string | — | Model tier used for the run being receipted. For validation rungs before calibrated expansion, use standard. |
session_id | string | — | Optional bootstrap/session identifier returned by orgx_bootstrap. |
artifact_id | string | — | Related artifact UUID to anchor the receipt to. Alternative to entity_type+entity_id when the proof lives in OrgX as an artifact. |
budget_mode | string | — | Budget posture used for the run being receipted. For validation rungs before calibrated expansion, use cheapest_valid. |
entity_type | string | — | Related entity type (initiative, workstream, milestone, task, decision). Required if no artifact_id is provided — pair with entity_id. |
max_cost_usd | number | — | Per-task or canary spend cap used during the validation run, when known. |
receipt_type | string | — | Receipt category key. Recognized values: "proof", "outcome", "quality", "attribution", "learning". Custom domain-specific keys are also accepted. |
Parameters from the server's own tool schema.
An AI agent can call orgx_submit_receipt faster than any human can review — one bad instruction and it creates or modifies resources in OrgX by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (35 properties)
Documented attack patterns abuse exactly the kind of access orgx_submit_receipt 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_submit_receipt:
{
"version": "1",
"default": "deny",
"tools": {
"orgx_submit_receipt": {
"limits": [
{
"counter": "orgx_submit_receipt_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}orgx_submit_receipt 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.
Free to start. No card required.
Submit a durable receipt (proof, outcome, quality, attribution, or learning) anchored to an OrgX entity or artifact. Required: receipt_type + summary. Strongly recommended: one anchor (entity_type+entity_id OR artifact_id), artifact_type, business_outcome, agent_type, AND at least one verifiable URL inside evidence. Recognized receipt_type: "proof" (completion proof), "outcome" (measurable result), "quality" (review/score), "attribution" (credit link to revenue/value), "learning" (distilled lesson). Custom keys also accepted. Recognized evidence shapes (mix and match): { prs: string[] } — GitHub PR URLs. { deploys: string[] } — deployment URLs. { test_runs: string[] } — CI run URLs. { metrics: { name, value, unit? }[] } — quantitative outcomes. { links: string[] }, { notes: string } — supporting URLs/text. Pass idempotency_key when retrying — server deduplicates. USE WHEN: closing the loop on agent work with provenance. For founder/team work, receipts should prove the practical artifact and its business outcome, not just say the agent finished. NEXT: orgx_recommend or orgx_search to find the next priority. DO NOT USE for telemetry — use orgx_emit_activity. It is categorised as a Write tool in the OrgX MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
orgx_submit_receipt accepts 12 parameters: summary, _context, evidence, entity_id, agent_type, model_tier, session_id, artifact_id, budget_mode, entity_type, max_cost_usd, receipt_type. 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_submit_receipt: 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_submit_receipt is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the orgx_submit_receipt 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_submit_receipt. 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_submit_receipt 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.