Get detail of a workflow. In workflow detail contain a list of stages and list of fields that used to create job In each field, it contains: - name: name of the field - code: code of the field - type: type of the field - required: true if the field is required - options: options of the field - pl...
AI agents call get_workflow to retrieve information from Rework MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries and returns workflow metadata. It has no side effects, does not modify data, execute code, delete anything, or involve financial transactions. The low severity reflects minimal blast radius if misused—an agent could only retrieve information about workflows.
From the tool's definition Tool retrieves workflow details including stages and field configurations. The description uses "Get detail" and specifies it returns structured information (name, code, type, required, options, placeholder) without any modification, creation, deletion, or…
Attacks that exploit this kind of access
Get detail of a workflow. In workflow detail contain a list of stages and list of fields that used to create job In each field, it contains: - name: name of the field - code: code of the field - type: type of the field - required: true if the field is required - options: options of the field - placeholder: description of the field. It is categorised as a Read tool in the Rework MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rework MCP Server MCP server in PolicyLayer and add a rule for get_workflow: 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 Rework MCP Server. Nothing to install.
get_workflow 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 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. 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 is provided by the Rework MCP Server MCP server (rework-com/rework-mcp-server). 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 →