get_execution_status

Get the status and results of a workflow execution. Use after execute_workflow with wait_for_completion=false.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_execution_status

What does the get_execution_status tool do? +

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.

How do I enforce a policy on get_execution_status? +

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.

What risk level is get_execution_status? +

get_execution_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_execution_status? +

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.

How do I block get_execution_status completely? +

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.

What MCP server provides get_execution_status? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FlowDot MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.