Check the status of a background job and retrieve results when available.
AI agents call get_job_status to retrieve information from USQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation: it queries the status of an existing job and retrieves its results. No data is created, modified, deleted, or destroyed. No code is executed, and no external side effects are triggered. Although it operates in a context where other tools on the server (execute_query, execute_script) can perform destructive or executable actions, get_job_status itself is purely informational.
From the tool's definition The tool 'get_job_status' retrieves status information about background jobs and their results. The description indicates it 'Check[s] the status' and 'retrieve[s] results' — operations that query or fetch data without modifying state.
Attacks that exploit this kind of access
Check the status of a background job and retrieve results when available. It is categorised as a Read tool in the USQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the USQL MCP Server 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 USQL MCP Server. Nothing to install.
get_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 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.
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.
get_job_status is provided by the USQL MCP Server MCP server (jvm/usql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →