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 queries and returns information about an existing workflow without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves metadata about a workflow configuration. The low severity reflects minimal risk—at worst, an agent could gain visibility into workflow details, which would not cause harm or unauthorized state changes.
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.
Attacks that exploit this kind of access
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 (liuchongchong1995/uns-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →