record_repeated_question
Track a question the user asked that NodeBench should have already known. This is the core failure signal — repeat cognition means the system isn
This record as markdown: /tools/io-github-homenshum-nodebench/record-repeated-question.md
What record_repeated_question does on Nodebench
AI agents use record_repeated_question to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why record_repeated_question is rated Medium
This tool writes/records a data point (a repeated question) to some internal tracking system. It creates or modifies stored records about user interactions. No code execution, deletion, or financial action is implied. Severity is low as it merely logs a quality signal with limited blast radius.
From the tool's definition 'Track a question the user asked' — records/stores data about repeated questions as a failure signal for the system
Attacks that exploit this kind of access
The rule that runs record_repeated_question 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 record_repeated_question, this is the rule to start with:
record_repeated_question stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 record_repeated_question call is checked against it from then on.
Questions about record_repeated_question
Track a question the user asked that NodeBench should have already known. This is the core failure signal — repeat cognition means the system isn. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for record_repeated_question: 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.
record_repeated_question is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the record_repeated_question 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 record_repeated_question. 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.
record_repeated_question 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