Get the current status of a specific workflow. Returns detailed information about workflow progress, current step, and any errors encountered.
AI agents call get_workflow_status to retrieve information from AWS without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about an existing workflow without modifying, deleting, or executing any operations. It is a passive data retrieval function analogous to 'get' or 'fetch' operations. The blast radius is minimal as misuse would only expose workflow status information, not alter infrastructure or execute code.
From the tool's definition Tool name 'get_workflow_status' and description 'Get the current status of a specific workflow' and 'Returns detailed information about workflow progress, current step, and any errors encountered' indicate a read-only query operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_workflow_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS, and nothing reaches the server without passing your rules. This is the rule we recommend for get_workflow_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_workflow_status": {}
}
}get_workflow_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.
Get the current status of a specific workflow. Returns detailed information about workflow progress, current step, and any errors encountered. It is categorised as a Read tool in the AWS MCP Server, which means it retrieves data without modifying state.
Register the AWS MCP server in PolicyLayer and add a rule for get_workflow_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 AWS. Nothing to install.
get_workflow_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_workflow_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_workflow_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_workflow_status is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
300 AWS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.