// SCAN REPORT

Stata

12 tools. 6 can modify or destroy data without limits.

5 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

6 can modify or destroy data

6 read-only

12 tools total

Community server · catalogue entry verified 12/06/2026

How to control Stata ↓

TOOL MAP

What Stata exposes to your agents

Read (6) Write / Execute (5) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Stata tools

Execute · High stata_run This tool runs commands in a live Stata session, which can perform data transformations, calculations, file I/O, and other operations whose effects depend on the command arguments. Execute · High stata_run_dofile This tool executes arbitrary Stata code via do files, which are executable scripts. Execute · High stata_install_package Installing packages fetches code from external sources and modifies the Stata installation environment. Write · High stata_write_dofile This tool creates and modifies files on disk by writing Stata code to do-files.

6 of Stata's 12 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Stata

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

Rate limit write operations

{
  "stata_append_dofile": {
    "limits": [
      {
        "counter": "stata_append_dofile_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "stata_get_data_info": {
    "limits": [
      {
        "counter": "stata_get_data_info_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 Stata — 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 STATA →

Free to start. No card required.

FULL CATALOGUE

All 12 Stata tools

EXECUTE 3 tools

Execute stata_run 在最近的 Stata MCP session_id 对应的 Stata GUI 中执行一条或多条 Stata 命令；可先用 stata_session(action= Execute stata_run_dofile 在 Stata GUI 中运行一个 do 文件。该工具以 session_id 表示一个复现任务/同一个 Stata GUI； Execute stata_install_package 在已打开的 Stata GUI 中安装外部包，如 estout、ivreg2、rdrobust 等

WRITE 2 tools

Write stata_append_dofile 向已有 do 文件追加内容 Write stata_write_dofile 将 Stata 代码写入 do 文件并保存到磁盘，返回文件路径；相对文件名会写入最近 session 项目的 .stata-mcp/dofiles/，不会使用 MCP runtime。

READ 6 tools

Read stata_get_data_info 在 Stata GUI 中显示当前数据集的基本信息 Read stata_get_data_schema 读取当前 Stata 数据集结构、缺失摘要和样本预览，返回给 Claude 分析 Read stata_get_results 在 Stata GUI 中显示上一次命令的 r() 或 e() 存储结果 Read stata_read_dofile 读取 do 文件内容，返回给 Claude 检查、解释或继续修改 Read stata_read_log 读取 Stata text log。path 留空时读取最近 session 的 last_log_path；推荐 output_format= Read stata_status 检查 Stata MCP 服务器状态、内存 session 和项目局部 .stata-mcp/cache/task_registry.json 中记录的 session/do/log 关系

OTHER 1 tools

Other stata_session 管理 Stata MCP session：列出、查询、销毁、切换最近 session。session_id 代表同一复现任务/同一个 Stata GUI，并关联 entry/source/current do、每个 do

EXPLORE

Related servers

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

FAQ

Questions about Stata

How do I prevent bulk modifications through Stata? +

The Stata server has 2 write tools including stata_append_dofile, stata_write_dofile. 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 Stata.

How many tools does the Stata MCP server expose? +

12 tools across 3 categories: Execute, Read, Write. 6 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Stata? +

Register the Stata 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 Stata tool call.

Deterministic rules across all 12 Stata tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON STATA →

Free to start. No card required.

12 Stata tools catalogued and risk-classified — across an index of 43,000+ MCP servers.