AI agents call list_jobs 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 'list_*' pattern across MCP servers typically indicates read-only operations that retrieve and display data. No evidence suggests data modification, deletion, execution, or financial operations. The lack of description lowers confidence slightly, but the naming pattern and context of job status management tools support a Read classification.
From the tool's definition Tool name 'list_jobs' with no description provided. Based on naming convention consistent with sibling tools like 'list_workflows' and 'get_job_status', this tool retrieves job information without side effects.
Documented attack patterns abuse exactly the kind of access list_jobs 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 list_jobs:
{
"version": "1",
"default": "deny",
"tools": {
"list_jobs": {}
}
}list_jobs 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_jobs. 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 list_jobs: 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.
list_jobs 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_jobs 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_jobs. 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_jobs 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.