record_manual_correction

Track a human correction to agent output. Every correction is evidence of a system gap — the system should have gotten this right.

SERVERNodebench SOURCEnodebench-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/record-manual-correction.md

What record_manual_correction does on Nodebench

AI agents use record_manual_correction 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_manual_correction is rated Medium

This tool records/writes correction data to a system. It creates a new record of a human correction, which is a reversible write operation with no code execution or destructive effects. Misuse could corrupt quality-gate feedback loops or bias the AI flywheel training signals, hence medium severity.

From the tool's definition Track a human correction to agent output

Risk signalsBulk/mass operation — affects multiple targets

Questions about record_manual_correction

What does the record_manual_correction tool do? +

Track a human correction to agent output. Every correction is evidence of a system gap — the system should have gotten this right. 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.

How do I enforce a policy on record_manual_correction? +

Register the Nodebench MCP server in PolicyLayer and add a rule for record_manual_correction: 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.

What risk level is record_manual_correction? +

record_manual_correction is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit record_manual_correction? +

Yes. Add a rate_limit block to the record_manual_correction 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.

How do I block record_manual_correction completely? +

Set action: deny in the PolicyLayer policy for record_manual_correction. 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.

What MCP server provides record_manual_correction? +

record_manual_correction 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nodebench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.