deal_autopsy
Tracked data-center M&A / capex deal flow with the DCPI grid-reality verdict overlaid on each deal market — "what is the real play?". Returns recent deals (buyer, seller, value, market) + each market DCPI verdict and time-to-power; with a paid key, the per-deal autopsy read (long-dated land/power...
This record as markdown: /tools/cloud-dchub-mcp-server/deal-autopsy.md
What deal_autopsy does on Mcp Server
AI agents call deal_autopsy to retrieve information from Mcp Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Number of recent deals to return (default ~15) |
comparables | string | — | Comparables detail: "none" (default — count only, cheapest), "summary" (top-2 grounding signals), or "full" (the complete cited set). Escalate only for deals yo |
Parameters from the server's own tool schema.
Why deal_autopsy is rated Low
The tool fetches and returns tracked M&A and capex deal data along with analytical overlays (DCPI verdicts, time-to-power). It is a read/query operation that retrieves intelligence about deals rather than executing, creating, or modifying them. Severity is medium because it surfaces sensitive M&A deal flow and market intelligence that could be commercially sensitive if misused.
From the tool's definition 'Tracked data-center M&A / capex deal flow' and 'Returns recent deals (buyer, seller, value, market)' — the tool retrieves and returns existing deal data and analytical verdicts
Attacks that exploit this kind of access
The rule that runs deal_autopsy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deal_autopsy, this is the rule to start with:
deal_autopsy is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Server, apply this rule, and every deal_autopsy call is checked against it from then on.
Questions about deal_autopsy
Tracked data-center M&A / capex deal flow with the DCPI grid-reality verdict overlaid on each deal market — "what is the real play?". Returns recent deals (buyer, seller, value, market) + each market DCPI verdict and time-to-power; with a paid key, the per-deal autopsy read (long-dated land/power option vs near-term build vs queue gamble). Progressive disclosure to keep the default cheap: by default each read ships only a comparables COUNT (the verdict text is always included); pass comparables="summary" for the top-2 grounding signals, or comparables="full" to expand the complete cited set for a deal you're drilling into. Try: deal_autopsy limit=15. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
deal_autopsy accepts 2 parameters: limit, comparables. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for deal_autopsy: 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 Mcp Server. Nothing to install.
deal_autopsy 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 deal_autopsy 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 deal_autopsy. 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.
deal_autopsy is provided by the Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue