attach_execution_evidence

Attach evidence to a live execution trace. Use for URLs, uploaded files, screenshots, render outputs, and truth-boundary notes that support or qualify the workflow output.

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/attach-execution-evidence.md

WHAT IT DOES

What attach_execution_evidence does on Nodebench

AI agents use attach_execution_evidence 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 attach_execution_evidence is rated Medium

This tool modifies execution trace data by attaching supporting evidence (URLs, files, screenshots, outputs, notes). It is a reversible write operation that adds or modifies metadata/annotations within a trace system, similar to adding comments or attachments to records.

From the tool's definition Attach evidence to a live execution trace. Use for URLs, uploaded files, screenshots, render outputs, and truth-boundary notes that support or qualify the workflow output.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

attach_execution_evidence Rate-limited

attach_execution_evidence 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": {
    "attach_execution_evidence": {
      "limits": [
        {
          "counter": "attach_execution_evidence_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 attach_execution_evidence call is checked against it from then on.

FAQ

Questions about attach_execution_evidence

What does the attach_execution_evidence tool do? +

Attach evidence to a live execution trace. Use for URLs, uploaded files, screenshots, render outputs, and truth-boundary notes that support or qualify the workflow 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.

How do I enforce a policy on attach_execution_evidence? +

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

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

Can I rate-limit attach_execution_evidence? +

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

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

attach_execution_evidence 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

generate_evidence_manifest on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

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