job_status

Return state and exit metadata for a background command job.

SERVERZebbern Kali MCP SOURCEzebbern/zebbern-kali-mcp

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/zebbern-zebbern-kali-mcp/job-status.md

WHAT IT DOES

What job_status does on Zebbern Kali MCP

AI agents call job_status to retrieve information from Zebbern Kali MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why job_status is rated Low

Queries job state and metadata without modifying or executing commands; read-only status inspection.

From the tool's definition Return state and exit metadata for a background command job.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs job_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Zebbern Kali MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For job_status, this is the rule to start with:

job_status Allowed

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": {
    "job_status": {}
  }
}

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

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

FAQ

Questions about job_status

What does the job_status tool do? +

Return state and exit metadata for a background command job. It is categorised as a Read tool in the Zebbern Kali MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on job_status? +

Register the Zebbern Kali MCP server in PolicyLayer and add a rule for 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 Zebbern Kali MCP. Nothing to install.

What risk level is job_status? +

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

Can I rate-limit job_status? +

Yes. Add a rate_limit block to the 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 job_status completely? +

Set action: deny in the PolicyLayer policy for 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 job_status? +

job_status is provided by the Zebbern Kali MCP server (zebbern/zebbern-kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Zebbern Kali, and thousands of servers like it.

This server

All 133 Zebbern Kali tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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