delta_memo
Create a decision-ready memo artifact. Produces a delta.memo packet with recommendation, variables, scenarios, and evidence. Shareable with teammates and stakeholders.
This record as markdown: /tools/io-github-homenshum-nodebench/delta-memo.md
What delta_memo does on Nodebench
AI agents use delta_memo 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 delta_memo is rated Medium
The tool generates a memo document with structured data (recommendation, variables, scenarios, evidence) and makes it shareable. This is a create/compose operation that generates new data artifacts, fitting the Write category. The severity is low because memos are informational documents without side effects on systems or data—they do not execute code, delete data, move money, or trigger external operations.
From the tool's definition Tool creates/produces artifacts ('Create a decision-ready memo artifact', 'Produces a delta.memo packet') which are reversible document objects that can be modified or deleted later.
Attacks that exploit this kind of access
The rule that runs delta_memo 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 delta_memo, this is the rule to start with:
delta_memo 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 delta_memo call is checked against it from then on.
Questions about delta_memo
Create a decision-ready memo artifact. Produces a delta.memo packet with recommendation, variables, scenarios, and evidence. Shareable with teammates and stakeholders. 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 delta_memo: 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.
delta_memo 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 delta_memo 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 delta_memo. 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.
delta_memo 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