Return workflow run state.
AI agents call get_workflow_run to retrieve information from Dag Planner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns the state of a workflow run without altering, executing, or deleting any data. It is a straightforward read operation that queries existing state. The verb 'Return' and lack of any action language (execute, create, delete, modify) confirm it belongs in the Read category. Severity is low because misuse would only expose information, not cause operational harm or resource exhaustion.
From the tool's definition Tool name 'get_workflow_run' and description 'Return workflow run state' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Return workflow run state. It is categorised as a Read tool in the Dag Planner MCP Server, which means it retrieves data without modifying state.
Register the Dag Planner MCP server in PolicyLayer and add a rule for get_workflow_run: 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 Dag Planner. Nothing to install.
get_workflow_run 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_run 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_run. 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_run is provided by the Dag Planner MCP server (shubhamnegi/dag-planner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →