get_execution_history

Get past execution history for a workflow including timestamps, status, and duration.

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-history.md

WHAT IT DOES

What get_execution_history does on FlowDot MCP Server

AI agents call get_execution_history 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.

RISK

Why get_execution_history is rated Low

This is a straightforward read operation that queries and retrieves historical data about workflow executions. There are no indications of capability to modify data, execute commands, delete records, or initiate financial transactions.

From the tool's definition The tool description states it retrieves 'past execution history for a workflow including timestamps, status, and duration' — purely informational queries with no modification, creation, or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_execution_history 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_history, this is the rule to start with:

get_execution_history Allowed

get_execution_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_execution_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every get_execution_history call is checked against it from then on.

FAQ

Questions about get_execution_history

What does the get_execution_history tool do? +

Get past execution history for a workflow including timestamps, status, and duration. 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_history? +

Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for get_execution_history: 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_history? +

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

Can I rate-limit get_execution_history? +

Yes. Add a rate_limit block to the get_execution_history 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_history completely? +

Set action: deny in the PolicyLayer policy for get_execution_history. 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_history? +

get_execution_history 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.

KEEP EXPLORING

More on FlowDot MCP Server, and thousands of servers like it.

This server

All 207 FlowDot MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →