get_gate_history

Get the history of quality gate runs for a given gate name. Shows pass/fail trend over time.

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/get-gate-history.md

WHAT IT DOES

What get_gate_history does on Nodebench

AI agents call get_gate_history 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 get_gate_history is rated Low

This tool retrieves and queries historical data about quality gate execution results. The verb 'Get' and the action of showing trends over time are consistent with Read operations. There is no creation, modification, deletion, code execution, or financial impact. The read-only nature is explicit in the description.

From the tool's definition Tool name 'get_gate_history' and description 'Get the history of quality gate runs for a given gate name. Shows pass/fail trend over time.' indicate retrieval of historical data with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_gate_history Allowed

get_gate_history 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": {
    "get_gate_history": {}
  }
}

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 get_gate_history call is checked against it from then on.

FAQ

Questions about get_gate_history

What does the get_gate_history tool do? +

Get the history of quality gate runs for a given gate name. Shows pass/fail trend over time. 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 get_gate_history? +

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

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

Can I rate-limit get_gate_history? +

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

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

get_gate_history 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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