compute_dimension_profile

Recompute and persist the DeepTrace dimension profile for an entity. Use after new company evidence, relationship updates, or temporal signals land.

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/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

Questions about compute_dimension_profile

What does the compute_dimension_profile tool do? +

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.

How do I enforce a policy on compute_dimension_profile? +

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.

What risk level is compute_dimension_profile? +

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

Can I rate-limit compute_dimension_profile? +

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.

How do I block compute_dimension_profile completely? +

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.

What MCP server provides compute_dimension_profile? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nodebench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.