run_do_file · Stata MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_do_file does on Stata MCP Server

AI agents invoke run_do_file to trigger actions in Stata MCP Server. 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.

WHY IT NEEDS A POLICY

Why run_do_file needs a policy

This tool executes Stata do-files, which are scripts containing arbitrary Stata commands. Execution of such scripts can perform side effects including data manipulation, file I/O, external commands, and computational operations whose outcomes depend on script contents.

From the tool's definition Tool name 'run_do_file' combined with description 'Stata에서 do 파일 실행' (Execute do file in Stata) indicates execution of arbitrary Stata code. The server context confirms it runs .do files which contain statistical analysis commands.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_do_file Rate-limited

run_do_file 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_do_file": {
      "limits": [
        {
          "counter": "run_do_file_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Stata MCP Server, so you can run agents against it safely.

FAQ

Questions about run_do_file

What does the run_do_file tool do? +

Stata에서 do 파일 실행. It is categorised as a Execute tool in the Stata MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_do_file? +

Register the Stata MCP Server MCP server in PolicyLayer and add a rule for run_do_file: 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 MCP Server. Nothing to install.

What risk level is run_do_file? +

run_do_file is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_do_file? +

Yes. Add a rate_limit block to the run_do_file 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.

How do I block run_do_file completely? +

Set action: deny in the PolicyLayer policy for run_do_file. 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.

What MCP server provides run_do_file? +

run_do_file is provided by the Stata MCP Server MCP server (mkprevo/stata-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.