Get the current status of a workflow execution
AI agents call get_execution_status to retrieve information from M I M I R Multi Agent Intelligent Memory & Insight Repository without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of an existing workflow execution. It retrieves information without modifying, executing, or deleting any data. Status checks are informational reads with no blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_execution_status' and description states 'Get the current status of a workflow execution' — this is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_execution_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and M I M I R Multi Agent Intelligent Memory & Insight Repository, and nothing reaches the server without passing your rules. This is the rule we recommend for get_execution_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_execution_status": {}
}
}get_execution_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
All 13 M I M I R Multi Agent Intelligent Memory & Insight Repository tools →
Get the current status of a workflow execution. It is categorised as a Read tool in the M I M I R Multi Agent Intelligent Memory & Insight Repository MCP Server, which means it retrieves data without modifying state.
Register the M I M I R Multi Agent Intelligent Memory & Insight Repository 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 M I M I R Multi Agent Intelligent Memory & Insight Repository. 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 M I M I R Multi Agent Intelligent Memory & Insight Repository MCP server (orneryd/mimir). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 M I M I R Multi Agent Intelligent Memory & Insight Repository tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 M I M I R Multi Agent Intelligent Memory & Insight Repository tools catalogued and risk-classified — across an index of 42,500+ MCP servers.