Get the execution history of a workflow. Shows past runs with their status and timing.
AI agents call birst_list_workflow_runs to retrieve information from Infor Birst MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays historical workflow execution data. It has no side effects—it does not create, modify, delete, or execute workflows. It is purely informational, allowing users to view past runs, their statuses, and timing information. This is a straightforward Read category operation.
From the tool's definition Tool description explicitly states 'Get the execution history of a workflow. Shows past runs with their status and timing.' This is a retrieval operation that queries historical data without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
Get the execution history of a workflow. Shows past runs with their status and timing. It is categorised as a Read tool in the Infor Birst MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Infor Birst MCP Server MCP server in PolicyLayer and add a rule for birst_list_workflow_runs: 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 Infor Birst MCP Server. Nothing to install.
birst_list_workflow_runs 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 birst_list_workflow_runs 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 birst_list_workflow_runs. 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.
birst_list_workflow_runs is provided by the Infor Birst MCP Server MCP server (mikahdev/infor-birst-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 →