ingest_dive_screenshots
Scan a directory for PNG/JPG screenshot files and bulk-import them into the dive session
This record as markdown: /tools/io-github-homenshum-nodebench/ingest-dive-screenshots.md
What ingest_dive_screenshots does on Nodebench
AI agents use ingest_dive_screenshots 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 ingest_dive_screenshots is rated Medium
The tool reads files from disk but its primary effect is bulk-importing (writing) those files into a dive session. This is a Write operation with medium severity since it could cause unintended bulk data injection into a session if misused, but it does not delete data or execute code.
From the tool's definition 'bulk-import them into the dive session' — the tool scans a directory and writes/imports screenshot files into a session
Attacks that exploit this kind of access
The rule that runs ingest_dive_screenshots 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 ingest_dive_screenshots, this is the rule to start with:
ingest_dive_screenshots 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 ingest_dive_screenshots call is checked against it from then on.
Questions about ingest_dive_screenshots
Scan a directory for PNG/JPG screenshot files and bulk-import them into the dive session. 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 ingest_dive_screenshots: 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.
ingest_dive_screenshots 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 ingest_dive_screenshots 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 ingest_dive_screenshots. 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.
ingest_dive_screenshots 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