get_workflow_history
Returns past runs for a specific workflow with scores, grades, step counts, and durations. Use to track conformance improvements over time and identify regression patterns.
This record as markdown: /tools/io-github-homenshum-nodebench/get-workflow-history.md
What get_workflow_history does on Nodebench
AI agents call get_workflow_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.
Why get_workflow_history is rated Low
This tool queries and retrieves workflow execution history (scores, grades, step counts, durations) without side effects. It is purely informational for tracking and analysis purposes. No data is modified, deleted, or external operations triggered. This is a straightforward Read operation with minimal risk if misused.
From the tool's definition Tool name 'get_workflow_history' and description 'Returns past runs' indicate retrieval of historical workflow data. No creation, modification, deletion, or execution of external systems described.
Attacks that exploit this kind of access
The rule that runs get_workflow_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_workflow_history, this is the rule to start with:
get_workflow_history 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_workflow_history call is checked against it from then on.
Questions about get_workflow_history
Returns past runs for a specific workflow with scores, grades, step counts, and durations. Use to track conformance improvements over time and identify regression patterns. 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_workflow_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.
get_workflow_history 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_workflow_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.
Set action: deny in the PolicyLayer policy for get_workflow_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.
get_workflow_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.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue