compute_dimension_profile
Recompute and persist the DeepTrace dimension profile for an entity. Use after new company evidence, relationship updates, or temporal signals land.
This record as markdown: /tools/io-github-homenshum-nodebench/compute-dimension-profile.md
What compute_dimension_profile does on Nodebench
AI agents use compute_dimension_profile 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 compute_dimension_profile is rated Medium
The tool computes and *persists* (writes/updates) a dimension profile for an entity. This is a reversible write operation — it updates stored data but does not irreversibly delete or destroy anything. Misuse could corrupt entity profiles used downstream by AI or analytics pipelines, giving it medium severity.
From the tool's definition Recompute and persist the DeepTrace dimension profile for an entity
Attacks that exploit this kind of access
The rule that runs compute_dimension_profile 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 compute_dimension_profile, this is the rule to start with:
compute_dimension_profile 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 compute_dimension_profile call is checked against it from then on.
Questions about compute_dimension_profile
Recompute and persist the DeepTrace dimension profile for an entity. Use after new company evidence, relationship updates, or temporal signals land. 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 compute_dimension_profile: 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.
compute_dimension_profile 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 compute_dimension_profile 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 compute_dimension_profile. 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.
compute_dimension_profile 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