generate_self_instructions
Generate self-instructions for the agent in various formats: skills_md (SKILL.md), rules_md (RULES.md), guidelines (internal), claude_md (CLAUDE.md). Includes authoritative source citations.
This record as markdown: /tools/io-github-homenshum-nodebench/generate-self-instructions.md
What generate_self_instructions does on Nodebench
AI agents use generate_self_instructions 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 generate_self_instructions is rated Medium
This tool creates new instruction/documentation files and modifies agent configuration data (self-instructions in multiple formats). While it generates text rather than executing arbitrary operations, it writes structured data that affects agent behavior and operations. This is reversible (files can be edited or deleted), so it falls under Write rather than Execute.
From the tool's definition Tool name contains 'generate' and description explicitly states it 'Generate self-instructions' in various formats including markdown files (SKILL.md, RULES.md, CLAUDE.md), which constitutes creating or modifying data.
Attacks that exploit this kind of access
The rule that runs generate_self_instructions 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 generate_self_instructions, this is the rule to start with:
generate_self_instructions 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 generate_self_instructions call is checked against it from then on.
Questions about generate_self_instructions
Generate self-instructions for the agent in various formats: skills_md (SKILL.md), rules_md (RULES.md), guidelines (internal), claude_md (CLAUDE.md). Includes authoritative source citations. 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 generate_self_instructions: 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.
generate_self_instructions 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 generate_self_instructions 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 generate_self_instructions. 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.
generate_self_instructions 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