get_job_status

Get the execution status of a job run by runId.

SERVERFrontmcp SOURCEagentfront/frontmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/frontmcp/get-job-status.md

WHAT IT DOES

What get_job_status does on Frontmcp

AI agents call get_job_status 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.

RISK

Why get_job_status is rated Low

This tool retrieves status information about a previously executed job using a runId parameter. It performs a read-only query with no side effects, no data modification, no code execution, and no destructive operations. The low severity reflects minimal blast radius—an AI agent misusing this tool could only access status information about existing jobs.

From the tool's definition Tool name 'get_job_status' and description 'Get the execution status of a job' indicate a retrieval operation that queries job status without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_job_status 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 get_job_status, this is the rule to start with:

get_job_status Allowed

get_job_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_job_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every get_job_status call is checked against it from then on.

FAQ

Questions about get_job_status

What does the get_job_status tool do? +

Get the execution status of a job run by runId. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_job_status? +

Register the Front MCP server in PolicyLayer and add a rule for get_job_status: 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.

What risk level is get_job_status? +

get_job_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_job_status? +

Yes. Add a rate_limit block to the get_job_status 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.

How do I block get_job_status completely? +

Set action: deny in the PolicyLayer policy for get_job_status. 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.

What MCP server provides get_job_status? +

get_job_status 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.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →