Low Risk

get_session_metrics

Get comprehensive metrics for all interactive OpenROAD sessions.

How to control get_session_metrics ↓

What get_session_metrics does on Openroad

AI agents call get_session_metrics to retrieve information from Openroad without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_session_metrics needs a policy

This tool retrieves and queries metrics data from OpenROAD sessions without creating, modifying, deleting, or executing operations. It has no side effects and falls squarely into the Read category with minimal security risk. Low severity because metrics queries are informational only.

From the tool's definition Tool description states 'Get comprehensive metrics' which is a retrieval operation with no modification capabilities. The verb 'Get' and the context of querying metrics from existing sessions indicates read-only access.

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

How to control get_session_metrics

PolicyLayer is an MCP gateway — it sits between your AI agents and Openroad, and nothing reaches the server without passing your rules. This is the rule we recommend for get_session_metrics:

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

get_session_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 Openroad — 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 get_session_metrics

What does the get_session_metrics tool do? +

Get comprehensive metrics for all interactive OpenROAD sessions. It is categorised as a Read tool in the Openroad MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_metrics? +

Register the Openroad MCP server in PolicyLayer and add a rule for get_session_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 Openroad. Nothing to install.

What risk level is get_session_metrics? +

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

Can I rate-limit get_session_metrics? +

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

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

get_session_metrics is provided by the Openroad MCP server (the-openroad-project/openroad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Openroad tool call.

Start from Openroad, 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.

10 Openroad 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.