check_job

Test-mode fal mirror.

SERVERLibi SOURCENagellabs/libi

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/libi/check-job.md

WHAT IT DOES

What check_job does on Libi

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

RISK

Why check_job is rated Low

Tool queries job state in a test environment; no creation, modification, deletion, or execution of external operations.

From the tool's definition Test-mode fal mirror; check_job likely retrieves job status without modifying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_job safely

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

check_job Allowed

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

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

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

FAQ

Questions about check_job

What does the check_job tool do? +

Test-mode fal mirror. It is categorised as a Read tool in the Libi MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_job? +

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

What risk level is check_job? +

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

Can I rate-limit check_job? +

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

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

check_job is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Libi, and thousands of servers like it.

This server

All 215 Libi tools →

Across the catalogue

The MCP Attack Database →

Guides

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