job.status
Get structured job state, result, error, and event history.
This record as markdown: /tools/visionmcp/job.status.md
What job.status does on Visionmcp
AI agents call job.status to retrieve information from Visionmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why job.status is rated Low
This tool retrieves information about job execution state without modifying, executing, or deleting any data. It is a straightforward status/monitoring query operation typical of observability endpoints.
From the tool's definition Tool name 'job.status' and description 'Get structured job state, result, error, and event history' indicate data retrieval only. The verb 'Get' and the passive nature of querying status/history confirm read-only behavior with no side effects.
Attacks that exploit this kind of access
The rule that runs job.status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, 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 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 Visionmcp, apply this rule, and every job.status call is checked against it from then on.
Questions about job.status
Get structured job state, result, error, and event history. It is categorised as a Read tool in the Visionmcp MCP Server, which means it retrieves data without modifying state.
Register the Vision 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 Visionmcp. Nothing to install.
job.status 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 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.
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.
job.status is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
This server
Across the catalogue