// SCAN REPORT

Xmo Data

5 tools. 2 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 7 Jul 2026

2 can modify or destroy data

3 read-only

5 tools total

Community server · catalogue entry checked 07/07/2026 · full schemas captured for 4 of 5 tools

How to control Xmo Data ↓

TOOL MAP

What Xmo Data exposes to your agents

Read (3) Write / Execute (1) Destructive / Financial (1)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Xmo Data costs in tokens

1,736 tokens of tool definitions, loaded on every request

0.9% of a 200k context window

861 heaviest tool: create_dataset

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Xmo Data tools

Destructive · High delete_dataset This tool irreversibly deletes entire datasets and their associated data. Write · Medium create_dataset This tool creates and persists new datasets in the system.

2 of Xmo Data's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Xmo Data

PolicyLayer is an MCP gateway — it sits between your AI agents and Xmo Data, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_dataset": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_dataset": {
    "limits": [
      {
        "counter": "create_dataset_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "download_dataset": {
    "limits": [
      {
        "counter": "download_dataset_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Xmo Data — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON XMO DATA →

Instant setup, no code required.

FULL CATALOGUE

All 5 Xmo Data tools

DESTRUCTIVE 1 tools

Destructive delete_dataset 删除指定的数据集以及关联的所有数据。此操作不可撤销，请谨慎操作。

WRITE 1 tools

Write create_dataset 创建新的数据集。需要先定义数据集的名称、时间范围和数据列配置。在创建列配置的时候一定要特别的注意参数，比如有些电力披露数据需要通过参数来指定省份，这个时候要按照示例中的格式传入列配置说明： - meta_name:

READ 3 tools

Read download_dataset 当用户希望查询数据集数据的时候，将数据集数据下载到CSV文件后，用户可以进行进一步的分析和处理。需要指定数据集名称、保存路径、时间范围和采样间隔。 ⚠️ 使用建议： - 当用户查询 7 天以上的数据：建议分批下载或使用 Read list_data_columns 列出所有可用的数据列元数据，包括系统列和用户自定义列。返回列的ID、名称、分类、描述、采样间隔和查询参数。当查找对应的数据列元数据的时候的时候，如果第一页中没有找到，可以尝试增加 page_no 和 page_size Read list_datasets 列出用户创建的所有数据集。返回数据集的基本信息，包括ID、名称和时间范围。

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Xmo Data

Can an AI agent delete data through the Xmo Data MCP server? +

Yes. The Xmo Data server exposes 1 destructive tools including delete_dataset. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Xmo Data? +

The Xmo Data server has 1 write tools including create_dataset. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Xmo Data.

How many tools does the Xmo Data MCP server expose? +

5 tools across 3 categories: Destructive, Read, Write. 3 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Xmo Data? +

Register the Xmo Data MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Xmo Data tool call.

Deterministic rules across all 5 Xmo Data tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON XMO DATA →

Instant setup, no code required.

5 Xmo Data tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Xmo Data's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →