Get workflows. Can filtered by q. Each workflow 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 -...
AI agents call get_workflows 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 tool retrieves and queries workflow information—it has no side effects, does not create, modify, delete, or execute operations. It is a straightforward read operation that fetches structured data about workflows and their associated stages and fields. Low severity because information disclosure about workflow configurations poses minimal risk; no data is modified or executed.
From the tool's definition Tool name is 'get_workflows' and description states 'Get workflows' with optional filtering by 'q'. Returns workflow metadata including stages and field configurations without modifying any data.
Attacks that exploit this kind of access
Get workflows. Can filtered by q. Each workflow 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_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 Rework MCP Server. Nothing to install.
get_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 get_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 get_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.
get_workflows 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 →