Get all task runs from the runner database. Optionally filter by status.
AI agents call get_task_runs to retrieve information from Qontinui 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 historical task execution records from a database and allows optional filtering by status. There is no creation, modification, deletion, or execution of workflows—only querying existing data. This is a classic Read operation with minimal risk even if misused by an agent, as it cannot trigger workflows, modify configurations, or cause unintended automation actions.
From the tool's definition Tool name 'get_task_runs' and description 'Get all task runs from the runner database. Optionally filter by status' indicate a data retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Get all task runs from the runner database. Optionally filter by status. It is categorised as a Read tool in the Qontinui MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qontinui MCP Server MCP server in PolicyLayer and add a rule for get_task_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 Qontinui MCP Server. Nothing to install.
get_task_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 get_task_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 get_task_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.
get_task_runs is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-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 →