Get detailed information about a specific workflow.
AI agents call get_workflow_info 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.
This tool retrieves and queries workflow metadata without creating, modifying, deleting, or executing any operations. It is a straightforward read operation consistent with the Read category (get, fetch). The blast radius of misuse is minimal—an agent could retrieve information about workflows, but cannot alter state or trigger external actions.
From the tool's definition Tool name 'get_workflow_info' and description 'Get detailed information about a specific workflow' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_workflow_info 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 get_workflow_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_workflow_info": {}
}
}get_workflow_info 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 detailed information about a specific workflow. 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 get_workflow_info: 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.
get_workflow_info 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_info 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_info. 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_info 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.