update_agents_md
Read, append, or update sections in the AGENTS.md file. This file contains instructions for AI agents working on the project. Use
This record as markdown: /tools/io-github-homenshum-nodebench/update-agents-md.md
What update_agents_md does on Nodebench
AI agents use update_agents_md 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 update_agents_md is rated Medium
This tool modifies a configuration/instruction file used by AI agents. While the changes are reversible (Write category, not Destructive), the severity is medium because corrupting or maliciously altering agent instructions could cause downstream issues in project automation, though the blast radius is limited to the specific file and recoverable.
From the tool's definition Tool description states 'Read, append, or update sections in the AGENTS.md file' - the operations 'append' and 'update' are write operations that modify file content reversibly.
Attacks that exploit this kind of access
The rule that runs update_agents_md 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 update_agents_md, this is the rule to start with:
update_agents_md 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 update_agents_md call is checked against it from then on.
Questions about update_agents_md
Read, append, or update sections in the AGENTS.md file. This file contains instructions for AI agents working on the project. Use. 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 update_agents_md: 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.
update_agents_md 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 update_agents_md 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 update_agents_md. 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.
update_agents_md 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