getSloMetricsSummary

Get SLO metrics for verification pipeline performance: latency percentiles, throughput, error rates.

SERVERNodebench SOURCEnodebench-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/getslometricssummary.md

What getSloMetricsSummary does on Nodebench

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

Why getSloMetricsSummary is rated Low

This tool queries and returns existing monitoring/observability data (latency percentiles, throughput, error rates) without modifying, deleting, or executing any operations. It is a passive read operation that presents no capability for data modification, execution, or financial impact. Severity is low because misuse would only expose metrics data, not enable harmful system changes.

From the tool's definition Tool retrieves SLO (Service Level Objective) metrics: 'Get SLO metrics for verification pipeline performance: latency percentiles, throughput, error rates.' The verbs 'get' and the read-only nature of metrics retrieval indicate data retrieval with no side…

Questions about getSloMetricsSummary

What does the getSloMetricsSummary tool do? +

Get SLO metrics for verification pipeline performance: latency percentiles, throughput, error rates. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getSloMetricsSummary? +

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

What risk level is getSloMetricsSummary? +

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

Can I rate-limit getSloMetricsSummary? +

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

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

getSloMetricsSummary is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Nodebench, 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 Nodebench'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.