invoke_view_tool

Invoke a per-view tool on the current or specified view.

SERVERNodebench SOURCEnodebench-mcp

High RISK CLASS

Category Execute

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/invoke-view-tool.md

WHAT IT DOES

What invoke_view_tool does on Nodebench

AI agents invoke invoke_view_tool to trigger actions in Nodebench. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why invoke_view_tool is rated High

This tool triggers execution of other tools dynamically based on parameters. The ability to invoke arbitrary per-view tools on specified views represents code/command execution with effects that vary by what tools are invoked and on which views.

From the tool's definition Tool name 'invoke_view_tool' combined with description 'Invoke a per-view tool on the current or specified view' indicates execution of arbitrary tools on views.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs invoke_view_tool 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 invoke_view_tool, this is the rule to start with:

invoke_view_tool Rate-limited

invoke_view_tool stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "invoke_view_tool": {
      "limits": [
        {
          "counter": "invoke_view_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every invoke_view_tool call is checked against it from then on.

FAQ

Questions about invoke_view_tool

What does the invoke_view_tool tool do? +

Invoke a per-view tool on the current or specified view. It is categorised as a Execute tool in the Nodebench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on invoke_view_tool? +

Register the Nodebench MCP server in PolicyLayer and add a rule for invoke_view_tool: 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 invoke_view_tool? +

invoke_view_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit invoke_view_tool? +

Yes. Add a rate_limit block to the invoke_view_tool 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 invoke_view_tool completely? +

Set action: deny in the PolicyLayer policy for invoke_view_tool. 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 invoke_view_tool? +

invoke_view_tool 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.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools → High-risk tools on this server →

Across the catalogue

qt_invoke_slot on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →