New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

runtime_assert_perf

Assert that live Performance monitors meet a caller-supplied baseline within tolerance (read-only). Capture the baseline earlier with runtime_get_monitors and pass it back inline. Pass direction is inferred (time/fps is higher-better; every other monitor is lower-better) unless overridden per key.

SERVERBreakpoint SOURCEbreakpoint-mcp
Low RISK CLASS
Category Read
Parameters 41 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/runtime-assert-perf.md

What runtime_assert_perf does on Breakpoint

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

ParameterTypeRequiredDescription
peer string Target a headless peer by id (from runtime_spawn_peers). Omit to address the default running game.
baseline object Yes Monitor key -> baseline value (capture earlier via runtime_get_monitors)
direction object Per-key override of the pass direction (defaults: time/fps higher_better, else lower_better)
tolerance number Fractional tolerance applied to each comparison (default 0 = exact)

Parameters from the server's own tool schema.

Why runtime_assert_perf is rated Low

This tool retrieves and validates performance monitor data against a supplied baseline. It has no side effects—it only asserts conditions and reports results. The read-only designation and comparison logic confirm it is a Read category tool with low severity, as misuse would only produce incorrect assertions without affecting system state or data integrity.

From the tool's definition Tool is explicitly described as "read-only" and performs assertion/validation checks against performance baselines.

Risk signalsBulk/mass operation — affects multiple targets

Questions about runtime_assert_perf

What does the runtime_assert_perf tool do? +

Assert that live Performance monitors meet a caller-supplied baseline within tolerance (read-only). Capture the baseline earlier with runtime_get_monitors and pass it back inline. Pass direction is inferred (time/fps is higher-better; every other monitor is lower-better) unless overridden per key. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.

What parameters does runtime_assert_perf accept? +

runtime_assert_perf accepts 4 parameters: peer, baseline, direction, tolerance. Required: baseline. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on runtime_assert_perf? +

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

What risk level is runtime_assert_perf? +

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

Can I rate-limit runtime_assert_perf? +

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

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Breakpoint's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.