Get detailed information about a specific run (experiment). 获取指定实验的详细信息。
AI agents call swanlab_get_run to retrieve information from Swanlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an experiment run without modifying, executing, or deleting any data. It is a straightforward read operation that queries existing data from SwanLab workspaces. No side effects or irreversible actions are possible. Low severity due to read-only nature and limited blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Get detailed information about a specific run (experiment)'. Server description explicitly specifies 'read-only access'. Tool name 'swanlab_get_run' follows read pattern (get, no mutation verbs).
Documented attack patterns abuse exactly the kind of access swanlab_get_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Swanlab, and nothing reaches the server without passing your rules. This is the rule we recommend for swanlab_get_run:
{
"version": "1",
"default": "deny",
"tools": {
"swanlab_get_run": {}
}
}swanlab_get_run 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.
Get detailed information about a specific run (experiment). 获取指定实验的详细信息。. It is categorised as a Read tool in the Swanlab MCP Server, which means it retrieves data without modifying state.
Register the Swanlab MCP server in PolicyLayer and add a rule for swanlab_get_run: 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 Swanlab. Nothing to install.
swanlab_get_run 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 swanlab_get_run 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 swanlab_get_run. 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.
swanlab_get_run is provided by the Swanlab MCP server (nexisato/swanlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Swanlab, 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.
11 Swanlab tools catalogued and risk-classified — across an index of 43,000+ MCP servers.