get_dimension_profile
Fetch the latest persisted DeepTrace dimension profile, including regime label, policy context, confidence, and the normalized dimension state.
This record as markdown: /tools/io-github-homenshum-nodebench/get-dimension-profile.md
What get_dimension_profile does on Nodebench
AI agents call get_dimension_profile 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 get_dimension_profile is rated Low
This tool retrieves and queries existing profile data without modification, deletion, or external operation execution. The verb 'fetch' and the absence of any language indicating state change, persistence, or triggering of external actions confirms it is a Read operation. Low severity because data retrieval poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name and description: 'Fetch the latest persisted DeepTrace dimension profile' — fetch is a retrieval operation with no side effects. Returns read-only data: regime label, policy context, confidence, and dimension state.
Attacks that exploit this kind of access
The rule that runs get_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 get_dimension_profile, this is the rule to start with:
get_dimension_profile 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 get_dimension_profile call is checked against it from then on.
Questions about get_dimension_profile
Fetch the latest persisted DeepTrace dimension profile, including regime label, policy context, confidence, and the normalized dimension state. 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 get_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.
get_dimension_profile 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 get_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 get_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.
get_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