Generate and persist an orchestration.consolidation_pass receipt for a GitHub pull request. USE WHEN: Eli or another engineering agent needs a durable PR review receipt with reading order, existence evidence, deduped findings, verdict, and server-derived AQ score. NEXT: inspect the returned artif...
AI agents call consolidate_pr to retrieve information from OrgX without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
pr_url | string | — | GitHub pull request URL, e.g. https://github.com/org/repo/pull/123 |
task_id | string | — | Task to attach the consolidation_pass artifact to |
verdict | string | — | Optional verdict override; defaults from PR state |
_context | object | — | Client context for conversation tracking (strongly recommended for cross-client continuity) |
commit_sha | string | — | Override commit SHA for idempotency; defaults to merge commit or PR head SHA |
decision_id | string | — | Decision to attach the consolidation_pass artifact to |
workspace_id | string | — | OrgX workspace UUID |
initiative_id | string | — | Initiative to attach the consolidation_pass artifact to |
reviewer_note | string | — | Optional reviewer note to include in critic evidence |
Parameters from the server's own tool schema.
Even though consolidate_pr 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.
Risk signalsHigh parameter count (25 properties)
Documented attack patterns abuse exactly the kind of access consolidate_pr 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 consolidate_pr:
{
"version": "1",
"default": "deny",
"tools": {
"consolidate_pr": {}
}
}consolidate_pr is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate and persist an orchestration.consolidation_pass receipt for a GitHub pull request. USE WHEN: Eli or another engineering agent needs a durable PR review receipt with reading order, existence evidence, deduped findings, verdict, and server-derived AQ score. NEXT: inspect the returned artifact_id or attach it to task completion proof. DO NOT USE WHEN: only asking for PR status; use GitHub tools instead. It is categorised as a Read tool in the OrgX MCP Server, which means it retrieves data without modifying state.
consolidate_pr accepts 9 parameters: pr_url, task_id, verdict, _context, commit_sha, decision_id, workspace_id, initiative_id, reviewer_note. 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 consolidate_pr: 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.
consolidate_pr is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the consolidate_pr 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 consolidate_pr. 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.
consolidate_pr 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.