export_dataset
Use when a user wants to pull their saved DC Hub shortlist OUT of the platform for offline analysis, a spreadsheet, or ingestion into another tool (PRO). Example: "Export my saved sites as GeoJSON for QGIS." — export_dataset format=geojson. Params: format ("csv" default, or "geojson"). Returns: t...
This record as markdown: /tools/cloud-dchub-mcp-server/export-dataset.md
What export_dataset does on Mcp Server
AI agents call export_dataset 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 |
|---|---|---|---|
format | string | — | Output file format: "csv" (default) or "geojson" (for GIS tools like QGIS) |
Parameters from the server's own tool schema.
Why export_dataset is rated Low
The tool retrieves and exports existing saved data in a chosen format (CSV or GeoJSON). It performs a read/export operation with no side effects—it does not create, modify, delete, or trigger any external operations. It simply returns the user's saved site data as text output.
From the tool's definition 'pull their saved DC Hub shortlist OUT of the platform for offline analysis', 'Returns: the full file contents as text — CSV rows or a GeoJSON FeatureCollection of your saved sites'
Attacks that exploit this kind of access
The rule that runs export_dataset 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 export_dataset, this is the rule to start with:
export_dataset 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 export_dataset call is checked against it from then on.
Questions about export_dataset
Use when a user wants to pull their saved DC Hub shortlist OUT of the platform for offline analysis, a spreadsheet, or ingestion into another tool (PRO). Example: "Export my saved sites as GeoJSON for QGIS." — export_dataset format=geojson. Params: format ("csv" default, or "geojson"). Returns: the full file contents as text — CSV rows or a GeoJSON FeatureCollection of your saved sites with DCPI score, target MW, market, coordinates, and notes. Do NOT use to list sites in-chat (use list_saved_sites) or to save a new one (use save_site); this is the bulk-download path. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
export_dataset accepts 1 parameter: format. 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 export_dataset: 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.
export_dataset 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 export_dataset 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 export_dataset. 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.
export_dataset 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