list_transactions
M&A and capital transactions in the data center sector — 1,400+ tracked deals (2019-present), each with its disclosed value where public (many private deals are undisclosed). Returns deal name, buyer, seller, value, date, market, target operator, type (acquisition/JV/refinance/recap). Filter by y...
This record as markdown: /tools/cloud-dchub-mcp-server/list-transactions.md
What list_transactions does on Mcp Server
AI agents call list_transactions 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 |
|---|---|---|---|
buyer | string | — | Filter by acquiring company name, e.g. Blackstone, KKR, Digital Realty |
limit | integer | — | Max results to return (1-500; default varies by tool) |
offset | integer | — | Pagination offset, 0-based (skip this many results) |
region | string | — | Geographic region filter, e.g. us, eu, apac, americas |
seller | string | — | Filter by selling/target company name, e.g. CyrusOne |
date_to | string | — | Latest deal date, ISO-8601 (YYYY-MM-DD) |
date_from | string | — | Earliest deal date, ISO-8601 (YYYY-MM-DD) |
deal_type | string | — | Deal type filter, e.g. acquisition, jv, refinance, recap |
max_value_usd | number | — | Maximum disclosed deal value in US dollars |
min_value_usd | number | — | Minimum disclosed deal value in US dollars, e.g. 1000000000 for $1B+ |
Parameters from the server's own tool schema.
Why list_transactions is rated Low
Even though list_transactions 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 (10 properties)
Attacks that exploit this kind of access
The rule that runs list_transactions 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 list_transactions, this is the rule to start with:
list_transactions 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 list_transactions call is checked against it from then on.
Questions about list_transactions
M&A and capital transactions in the data center sector — 1,400+ tracked deals (2019-present), each with its disclosed value where public (many private deals are undisclosed). Returns deal name, buyer, seller, value, date, market, target operator, type (acquisition/JV/refinance/recap). Filter by year, min_value_usd, region, buyer, or target. Try: list_transactions year=2026 min_value_usd=1000000000. Broad M&A and capital-deal flow with filters; do NOT use for hyperscaler-specific lease/PPA/JV activity (use hyperscaler_deals) or a single-deal post-mortem (use deal_autopsy). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
list_transactions accepts 10 parameters: buyer, limit, offset, region, seller, date_to, date_from, deal_type, max_value_usd, min_value_usd. 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 list_transactions: 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.
list_transactions 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 list_transactions 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 list_transactions. 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.
list_transactions 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