list_dimension_interactions
List stored interaction effects for an entity, such as capital plus investor quality reducing execution fragility or narrative outpacing evidence.
This record as markdown: /tools/io-github-homenshum-nodebench/list-dimension-interactions.md
What list_dimension_interactions does on Nodebench
AI agents call list_dimension_interactions 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 list_dimension_interactions is rated Low
This tool retrieves or queries stored interaction effects data with no capability to modify, delete, or execute external operations. It is purely informational in nature, examining relationships like 'capital plus investor quality reducing execution fragility.' The use of 'List' and 'stored' clearly indicates data retrieval with no side effects, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'list_dimension_interactions' and description 'List stored interaction effects' indicate a retrieval operation that queries and returns existing data about interaction effects for an entity.
Attacks that exploit this kind of access
The rule that runs list_dimension_interactions 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 list_dimension_interactions, this is the rule to start with:
list_dimension_interactions 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 list_dimension_interactions call is checked against it from then on.
Questions about list_dimension_interactions
List stored interaction effects for an entity, such as capital plus investor quality reducing execution fragility or narrative outpacing evidence. 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 list_dimension_interactions: 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.
list_dimension_interactions 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 list_dimension_interactions 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 list_dimension_interactions. 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.
list_dimension_interactions 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