getCanaryTrend
Get canary benchmark trend: throughput score, quality score, verdict, and delta over time.
This record as markdown: /tools/io-github-homenshum-nodebench/getcanarytrend.md
What getCanaryTrend does on Nodebench
AI agents call getCanaryTrend 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 getCanaryTrend is rated Low
This is a query/fetch operation that retrieves benchmark trend data without side effects. The verb 'Get' and the nature of returning historical metrics (scores, verdicts, deltas) confirm this is a Read operation with minimal risk.
From the tool's definition Tool name and description indicate data retrieval only: 'Get canary benchmark trend' with retrieval of 'throughput score, quality score, verdict, and delta over time.' No modification, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
The rule that runs getCanaryTrend 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 getCanaryTrend, this is the rule to start with:
getCanaryTrend 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 getCanaryTrend call is checked against it from then on.
Questions about getCanaryTrend
Get canary benchmark trend: throughput score, quality score, verdict, and delta over time. 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 getCanaryTrend: 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.
getCanaryTrend 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 getCanaryTrend 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 getCanaryTrend. 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.
getCanaryTrend 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