get_workflow_schema
AI agents call get_workflow_schema to retrieve information from Workflows without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves workflow schema information, a read-only operation. Even without a description, the naming pattern ('get_*') and context within a workflows server indicate data retrieval. No modification, execution, deletion, or financial impact is implied. Confidence is moderate due to missing description.
From the tool's definition Tool name 'get_workflow_schema' indicates schema retrieval. Description is empty, limiting evidence; however, 'get' and 'schema' suggest a query operation that retrieves metadata without side effects.
Documented attack patterns abuse exactly the kind of access get_workflow_schema gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Workflows, and nothing reaches the server without passing your rules. This is the rule we recommend for get_workflow_schema:
{
"version": "1",
"default": "deny",
"tools": {
"get_workflow_schema": {}
}
}get_workflow_schema 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_workflow_schema. It is categorised as a Read tool in the Workflows MCP Server, which means it retrieves data without modifying state.
Register the Workflows MCP server in PolicyLayer and add a rule for get_workflow_schema: 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 Workflows. Nothing to install.
get_workflow_schema 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_schema 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_schema. 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_schema is provided by the Workflows MCP server (qtsone/workflows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Workflows, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Workflows tools catalogued and risk-classified — across an index of 43,000+ MCP servers.