runtime_get_monitors
Read live Performance monitors (FPS, draw calls, node count, physics, audio output latency, ...). Pass specific keys or omit for all. Keys include time/fps, render/total_draw_calls, audio/output_latency.
This record as markdown: /tools/breakpoint-mcp/runtime-get-monitors.md
What runtime_get_monitors does on Breakpoint
AI agents call runtime_get_monitors to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
keys | array | — | |
peer | string | — | Target a headless peer by id (from runtime_spawn_peers). Omit to address the default running game. |
Parameters from the server's own tool schema.
Why runtime_get_monitors is rated Low
This tool retrieves performance telemetry data without side effects. It queries existing monitoring data and returns values based on specified keys or defaults to all metrics. This is a pure read operation with no capability to modify system state, execute code, or affect application behavior beyond observation.
From the tool's definition Tool description explicitly states 'Read live Performance monitors' and lists retrieval of metrics (FPS, draw calls, node count, physics, audio output latency). No modification, deletion, execution, or financial operations described.
Attacks that exploit this kind of access
The rule that runs runtime_get_monitors safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runtime_get_monitors, this is the rule to start with:
runtime_get_monitors is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every runtime_get_monitors call is checked against it from then on.
Questions about runtime_get_monitors
Read live Performance monitors (FPS, draw calls, node count, physics, audio output latency, ...). Pass specific keys or omit for all. Keys include time/fps, render/total_draw_calls, audio/output_latency. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
runtime_get_monitors accepts 2 parameters: keys, peer. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for runtime_get_monitors: 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 Breakpoint. Nothing to install.
runtime_get_monitors 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 runtime_get_monitors 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 runtime_get_monitors. 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.
runtime_get_monitors is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue