Get the status of an automation execution.
AI agents call get_execution_status to retrieve information from Qontinui Web 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 status information about an ongoing or completed automation execution. It performs a read-only query against execution state without modifying, deleting, or triggering any actions. The verb 'Get' and lack of any write/execute/destructive language confirm it is a Read operation with minimal risk.
From the tool's definition Tool name 'get_execution_status' and description 'Get the status of an automation execution' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the status of an automation execution. It is categorised as a Read tool in the Qontinui Web MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qontinui Web MCP Server MCP server in PolicyLayer and add a rule for get_execution_status: 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 Web MCP Server. Nothing to install.
get_execution_status 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_execution_status 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_execution_status. 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_execution_status is provided by the Qontinui Web MCP Server MCP server (qontinui/qontinui-web-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 →