query_view_data

Query data from a view

SERVERNodebench SOURCEnodebench-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/query-view-data.md

WHAT IT DOES

What query_view_data does on Nodebench

AI agents call query_view_data 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.

RISK

Why query_view_data is rated Low

The verb 'query' combined with 'view_data' clearly indicates data retrieval with no side effects. No language suggesting writes, deletions, code execution, or financial operations is present. This is a straightforward Read operation with minimal risk.

From the tool's definition Tool name 'query_view_data' and description 'Query data from a view' indicate a read operation that retrieves data from an existing view without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

query_view_data Allowed

query_view_data is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_view_data": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about query_view_data

What does the query_view_data tool do? +

Query data from a view. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_view_data? +

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

query_view_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_view_data? +

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

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

query_view_data 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 →

Across the catalogue

claude_query on Claude Bridge →collect_devtools_data on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →