mcp_check_job_status
AI agents call mcp_check_job_status to retrieve information from Databricks MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Status checks are informational queries that retrieve the current state of a job without side effects. This aligns with the 'Read' category (retrieves data; no side effects). Confidence is slightly reduced (0.85 rather than higher) due to the empty description, which prevents confirmation of exact behavior, but the naming convention and context strongly suggest a read-only operation.
From the tool's definition Tool name 'mcp_check_job_status' indicates a status-checking operation. The verb 'check' and noun 'status' imply querying/retrieving job state information without modification.
Attacks that exploit this kind of access
mcp_check_job_status. It is categorised as a Read tool in the Databricks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for mcp_check_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 Databricks MCP Server. Nothing to install.
mcp_check_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 mcp_check_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 mcp_check_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.
mcp_check_job_status is provided by the Databricks MCP Server MCP server (stephenjhsu/databricks-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 →