merge_compose_output
Judge-gated merge of subtask artifacts into a composed output.
This record as markdown: /tools/io-github-homenshum-nodebench/merge-compose-output.md
What merge_compose_output does on Nodebench
AI agents use merge_compose_output 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 merge_compose_output is rated Medium
This tool creates or modifies data by merging artifacts together. It is reversible (can be undone or re-run with different inputs) and does not delete data or execute arbitrary code, placing it in the Write category. Severity is medium because the output composition could impact downstream processes, but the judge-gating mechanism reduces risk of unchecked misuse.
From the tool's definition Tool performs a 'merge' operation that combines 'subtask artifacts into a composed output', which is a data modification/creation action. The 'judge-gated' qualifier indicates controls are in place but does not change the fundamental Write classification.
Attacks that exploit this kind of access
The rule that runs merge_compose_output 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 merge_compose_output, this is the rule to start with:
merge_compose_output 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 merge_compose_output call is checked against it from then on.
Questions about merge_compose_output
Judge-gated merge of subtask artifacts into a composed output. 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 merge_compose_output: 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.
merge_compose_output 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 merge_compose_output 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 merge_compose_output. 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.
merge_compose_output 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