读取 Stata text log。path 留空时读取最近 session 的 last_log_path；推荐 output_format=
AI agents call stata_read_log to retrieve information from Stata without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries log file data from a Stata session. It has no side effects on the underlying data or system state—it only reads previously generated log output. This is a pure read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'stata_read_log' and description indicate it 'reads' (读取) Stata text log files. The function retrieves log output from a session without modifying, executing, or deleting data.
Documented attack patterns abuse exactly the kind of access stata_read_log 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_read_log:
{
"version": "1",
"default": "deny",
"tools": {
"stata_read_log": {}
}
}stata_read_log is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
读取 Stata text log。path 留空时读取最近 session 的 last_log_path；推荐 output_format=. It is categorised as a Read tool in the Stata MCP Server, which means it retrieves data without modifying state.
Register the Stata MCP server in PolicyLayer and add a rule for stata_read_log: 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_read_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the stata_read_log 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_read_log. 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_read_log 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.