Check status of background operations (moves, optimizations, etc.)
AI agents call check_jobs to retrieve information from Mediabox MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the state of background operations without creating, modifying, deleting, or executing any actions. It is purely informational, similar to 'get_library_state' and 'activity_log' on the same server. The blast radius of misuse is minimal—an agent querying job status cannot harm the system.
From the tool's definition Tool name 'check_jobs' and description 'Check status of background operations' indicate a query/monitoring function with no modification or side effects.
Documented attack patterns abuse exactly the kind of access check_jobs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mediabox MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for check_jobs:
{
"version": "1",
"default": "deny",
"tools": {
"check_jobs": {}
}
}check_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.
Check status of background operations (moves, optimizations, etc.). It is categorised as a Read tool in the Mediabox MCP MCP Server, which means it retrieves data without modifying state.
Register the Mediabox MCP server in PolicyLayer and add a rule for check_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 Mediabox MCP. Nothing to install.
check_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 check_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 check_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.
check_jobs is provided by the Mediabox MCP server (juancmpdev/mediabox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mediabox MCP, 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.
30 Mediabox MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.