list_jobs
List registered jobs with optional filtering by tags or labels.
This record as markdown: /tools/frontmcp/list-jobs.md
What list_jobs does on Frontmcp
AI agents call list_jobs to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_jobs is rated Low
This tool retrieves information about registered jobs with optional filters. It performs no modifications, deletions, or execution of jobs—only retrieval and display of metadata. This is a classic Read category tool with minimal security risk unless the job data itself contains sensitive information, but the tool itself does not perform destructive, financial, or executable operations.
From the tool's definition Tool name 'list_jobs' and description 'List registered jobs with optional filtering by tags or labels' indicate a retrieval operation with no side effects. The verb 'List' and qualifier 'optional filtering' confirm this is a query/read action.
Attacks that exploit this kind of access
The rule that runs list_jobs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_jobs, this is the rule to start with:
list_jobs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every list_jobs call is checked against it from then on.
Questions about list_jobs
List registered jobs with optional filtering by tags or labels. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front 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 Frontmcp. 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 Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue