get_workflow_status

Get the current status of a specific workflow. Returns detailed information about workflow progress, current step, and any errors encountered.

SERVERAWS SOURCE@awslabs/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/aws/get-workflow-status.md

WHAT IT DOES

What get_workflow_status does on AWS

AI agents call get_workflow_status to retrieve information from AWS 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_workflow_status is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_workflow_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_workflow_status, this is the rule to start with:

get_workflow_status Allowed

get_workflow_status 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_workflow_status": {}
  }
}

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

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

FAQ

Questions about get_workflow_status

What does the get_workflow_status tool do? +

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.

How do I enforce a policy on get_workflow_status? +

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.

What risk level is get_workflow_status? +

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

Can I rate-limit get_workflow_status? +

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.

How do I block get_workflow_status completely? +

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.

What MCP server provides get_workflow_status? +

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.

KEEP EXPLORING

More on AWS, and thousands of servers like it.

This server

All 300 AWS tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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