get_execution_status
Get the status and results of a workflow execution. Use after execute_workflow with wait_for_completion=false.
This record as markdown: /tools/flowdot-llc-mcp-server/get-execution-status.md
What get_execution_status does on FlowDot MCP Server
AI agents call get_execution_status to retrieve information from FlowDot MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_execution_status is rated Low
This tool retrieves execution status and results from a completed or in-progress workflow. It is a query operation that has no side effects, does not modify data, and does not trigger external actions. It falls squarely into the Read category. Severity is low because retrieving execution status poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states 'Get the status and results of a workflow execution' - the verb 'get' indicates retrieval of data with no side effects.
Attacks that exploit this kind of access
The rule that runs get_execution_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_execution_status, this is the rule to start with:
get_execution_status 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 FlowDot MCP Server, apply this rule, and every get_execution_status call is checked against it from then on.
Questions about get_execution_status
Get the status and results of a workflow execution. Use after execute_workflow with wait_for_completion=false. It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FlowDot 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 FlowDot 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 FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue