Low Risk

swanlab_get_run_metrics

Get metric data for a run (experiment). Returns a list of metric records.

How to control swanlab_get_run_metrics ↓

What swanlab_get_run_metrics does on Swanlab

AI agents call swanlab_get_run_metrics 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.

Low Risk

Why swanlab_get_run_metrics needs a policy

This tool performs a data retrieval operation with no side effects. It queries and returns metric data from a SwanLab run/experiment. All sibling tools are read-only list/get operations, confirming the server's read-only nature. No creation, modification, deletion, code execution, or financial operations are involved.

From the tool's definition Server description states 'read-only access' and tool description says 'Get metric data for a run' which retrieves data without modification. The tool name includes 'get_' pattern and returns metric records.

Documented attack patterns abuse exactly the kind of access swanlab_get_run_metrics gives an agent:

How to control swanlab_get_run_metrics

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_metrics:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "swanlab_get_run_metrics": {}
  }
}

swanlab_get_run_metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Swanlab — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about swanlab_get_run_metrics

What does the swanlab_get_run_metrics tool do? +

Get metric data for a run (experiment). Returns a list of metric records. It is categorised as a Read tool in the Swanlab MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on swanlab_get_run_metrics? +

Register the Swanlab MCP server in PolicyLayer and add a rule for swanlab_get_run_metrics: 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.

What risk level is swanlab_get_run_metrics? +

swanlab_get_run_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit swanlab_get_run_metrics? +

Yes. Add a rate_limit block to the swanlab_get_run_metrics 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 swanlab_get_run_metrics completely? +

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

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

Enforce policy on every Swanlab tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.