getSloMetricsSummary
Get SLO metrics for verification pipeline performance: latency percentiles, throughput, error rates.
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…
Attacks that exploit this kind of access
The rule that runs getSloMetricsSummary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getSloMetricsSummary, this is the rule to start with:
getSloMetricsSummary 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 Nodebench, apply this rule, and every getSloMetricsSummary call is checked against it from then on.
Questions about getSloMetricsSummary
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.
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.
getSloMetricsSummary 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 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.
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.
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.
This server
Across the catalogue