record_path_step

Record a navigation/exploration step in the user

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-path-step.md

WHAT IT DOES

What record_path_step does on Nodebench

AI agents use record_path_step 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.

RISK

Why record_path_step is rated Medium

The tool records (writes) a navigation or exploration step, creating a new data entry. This is a reversible write operation with medium severity since it stores user activity data. Confidence is moderate because the description is truncated and full scope is unclear.

From the tool's definition "Record a navigation/exploration step" — creates/writes a step record

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs record_path_step 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_path_step, this is the rule to start with:

record_path_step Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_path_step": {
      "limits": [
        {
          "counter": "record_path_step_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every record_path_step call is checked against it from then on.

FAQ

Questions about record_path_step

What does the record_path_step tool do? +

Record a navigation/exploration step in the user. 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_path_step? +

Register the Nodebench MCP server in PolicyLayer and add a rule for record_path_step: 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_path_step? +

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

Can I rate-limit record_path_step? +

Yes. Add a rate_limit block to the record_path_step 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_path_step completely? +

Set action: deny in the PolicyLayer policy for record_path_step. 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_path_step? +

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

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →