export_dimension_bundle
Export the full DeepTrace dimension bundle for an entity: latest profile, snapshots, evidence, and interaction effects in one response.
This record as markdown: /tools/io-github-homenshum-nodebench/export-dimension-bundle.md
What export_dimension_bundle does on Nodebench
AI agents call export_dimension_bundle to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why export_dimension_bundle is rated Low
The tool exports/retrieves a comprehensive bundle of data (profiles, snapshots, evidence, interaction effects) for an entity. This is a read/fetch operation with no indication of side effects or data modification. Severity is medium because it aggregates potentially sensitive data about an entity into a single response, which could be misused for data exfiltration.
From the tool's definition Export the full DeepTrace dimension bundle... latest profile, snapshots, evidence, and interaction effects in one response
Attacks that exploit this kind of access
The rule that runs export_dimension_bundle 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 export_dimension_bundle, this is the rule to start with:
export_dimension_bundle is read-only, so it stays allowed. 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 export_dimension_bundle call is checked against it from then on.
Questions about export_dimension_bundle
Export the full DeepTrace dimension bundle for an entity: latest profile, snapshots, evidence, and interaction effects in one response. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for export_dimension_bundle: 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.
export_dimension_bundle is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the export_dimension_bundle 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 export_dimension_bundle. 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.
export_dimension_bundle 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