getComparisonTrend
Get baseline comparison trend for a benchmark family (investigation, canary, etc.).
This record as markdown: /tools/io-github-homenshum-nodebench/getcomparisontrend.md
What getComparisonTrend does on Nodebench
AI agents call getComparisonTrend 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 getComparisonTrend is rated Low
This tool retrieves or queries benchmark comparison trend data for analysis purposes. There is no indication of data modification, deletion, code execution, or financial impact. The operation is informational and non-mutating, fitting the 'Read' category. Low severity because misuse would only expose existing benchmark data without enabling destructive or dangerous actions.
From the tool's definition Tool name 'getComparisonTrend' and description 'Get baseline comparison trend for a benchmark family' indicate data retrieval without side effects. The verb 'Get' and the passive context of querying benchmark trends suggests a read-only operation.
Attacks that exploit this kind of access
The rule that runs getComparisonTrend 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 getComparisonTrend, this is the rule to start with:
getComparisonTrend 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 getComparisonTrend call is checked against it from then on.
Questions about getComparisonTrend
Get baseline comparison trend for a benchmark family (investigation, canary, etc.). 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 getComparisonTrend: 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.
getComparisonTrend 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 getComparisonTrend 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 getComparisonTrend. 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.
getComparisonTrend 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