get_repeat_cognition_metrics
The key compound metric. Measures repeat question rate, manual reconstruction count, packet abandonment rate, delegation-without-restatement rate, and average time-to-useful-output.
This record as markdown: /tools/io-github-homenshum-nodebench/get-repeat-cognition-metrics.md
What get_repeat_cognition_metrics does on Nodebench
AI agents call get_repeat_cognition_metrics 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 get_repeat_cognition_metrics is rated Low
The tool retrieves and measures pre-existing metrics related to cognition performance. The verb 'measures' and the focus on analyzing quantitative data (rates, counts, averages) indicate a pure Read operation that queries existing information without modifying, creating, deleting, or executing any external operations. There is no indication of state changes or irreversible actions.
From the tool's definition 'Measures repeat question rate, manual reconstruction count, packet abandonment rate, delegation-without-restatement rate, and average time-to-useful-output' — this tool retrieves and queries metrics data with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs get_repeat_cognition_metrics 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 get_repeat_cognition_metrics, this is the rule to start with:
get_repeat_cognition_metrics 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 get_repeat_cognition_metrics call is checked against it from then on.
Questions about get_repeat_cognition_metrics
The key compound metric. Measures repeat question rate, manual reconstruction count, packet abandonment rate, delegation-without-restatement rate, and average time-to-useful-output. 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 get_repeat_cognition_metrics: 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.
get_repeat_cognition_metrics 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 get_repeat_cognition_metrics 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 get_repeat_cognition_metrics. 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.
get_repeat_cognition_metrics 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