在 Stata GUI 中运行一个 do 文件。该工具以 session_id 表示一个复现任务/同一个 Stata GUI；
AI agents invoke stata_run_dofile to trigger actions in Stata. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes arbitrary Stata code via do files, which are executable scripts. While not destructive by design, do files can modify data, perform system calls, and trigger external operations. The severity is high because a malicious do file could corrupt data, exfiltrate information, or compromise system integrity.
From the tool's definition Tool description states '在 Stata GUI 中运行一个 do 文件' (run a do file in Stata GUI). Do files are arbitrary scripts containing Stata commands that can perform statistical analysis, data manipulation, file I/O, and system operations.
Documented attack patterns abuse exactly the kind of access stata_run_dofile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Stata, and nothing reaches the server without passing your rules. This is the rule we recommend for stata_run_dofile:
{
"version": "1",
"default": "deny",
"tools": {
"stata_run_dofile": {
"limits": [
{
"counter": "stata_run_dofile_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stata_run_dofile stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
在 Stata GUI 中运行一个 do 文件。该工具以 session_id 表示一个复现任务/同一个 Stata GUI；. It is categorised as a Execute tool in the Stata MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Stata MCP server in PolicyLayer and add a rule for stata_run_dofile: 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 Stata. Nothing to install.
stata_run_dofile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stata_run_dofile 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 stata_run_dofile. 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.
stata_run_dofile is provided by the Stata MCP server (shichengg/stata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Stata, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Stata tools catalogued and risk-classified — across an index of 43,000+ MCP servers.