在已打开的 Stata GUI 中安装外部包，如 estout、ivreg2、rdrobust 等
AI agents invoke stata_install_package 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.
Installing packages fetches code from external sources and modifies the Stata installation environment. This is not a simple write operation — it executes installation procedures, runs external network requests, and deploys executable code into the system. Misuse could introduce malicious or untrusted packages, making severity high.
From the tool's definition 安装外部包 (installs external packages) such as estout, ivreg2, rdrobust — triggers external operations by downloading and installing third-party software into the Stata environment
Documented attack patterns abuse exactly the kind of access stata_install_package 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_install_package:
{
"version": "1",
"default": "deny",
"tools": {
"stata_install_package": {
"limits": [
{
"counter": "stata_install_package_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stata_install_package 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 中安装外部包，如 estout、ivreg2、rdrobust 等. 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_install_package: 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_install_package 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_install_package 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_install_package. 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_install_package 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.