List workflow YAML files in a directory.
AI agents call list_workflows to retrieve information from Srunx 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 workflow files without creating, modifying, deleting, or executing anything. It is a pure read operation with minimal blast radius—an AI agent listing workflows poses no direct risk to system state or job execution.
From the tool's definition Tool name 'list_workflows' and description 'List workflow YAML files in a directory' indicate a retrieval operation with no modification or execution of the listed resources.
Documented attack patterns abuse exactly the kind of access list_workflows gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Srunx, and nothing reaches the server without passing your rules. This is the rule we recommend for list_workflows:
{
"version": "1",
"default": "deny",
"tools": {
"list_workflows": {}
}
}list_workflows 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.
List workflow YAML files in a directory. It is categorised as a Read tool in the Srunx MCP Server, which means it retrieves data without modifying state.
Register the Srunx MCP server in PolicyLayer and add a rule for list_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 Srunx. Nothing to install.
list_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 list_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 list_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.
list_workflows is provided by the Srunx MCP server (ksterx/srunx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Srunx, 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.
14 Srunx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.