AI agents call list_workflows to retrieve information from Unstructured API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' operation is a standard query/retrieval action with no side effects—it returns information about existing workflows without modifying, executing, or deleting anything. The empty description lowers confidence slightly, but the naming pattern and context from sibling tools clearly establish this as a Read operation with low severity impact.
From the tool's definition Tool name 'list_workflows' indicates retrieval of workflow information; server description confirms this server provides tools to 'list' workflows; sibling tool 'list_workflows_with_finished_jobs' reinforces listing as a read operation.
Documented attack patterns abuse exactly the kind of access list_workflows gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unstructured API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_workflows:
{
"version": "1",
"default": "deny",
"tools": {
"list_workflows": {}
}
}list_workflows 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.
list_workflows. It is categorised as a Read tool in the Unstructured API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unstructured API MCP Server MCP server in PolicyLayer and add a rule for list_workflows: 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 Unstructured API MCP Server. Nothing to install.
list_workflows 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 list_workflows 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 list_workflows. 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.
list_workflows is provided by the Unstructured API MCP Server MCP server (unstructured-io/uns-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Unstructured API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 Unstructured API MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.