AI agents call get-job-runs to retrieve information from Databricks Unity Catalog MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about job execution history without modifying, executing, or deleting any data. Misuse would only expose metadata that may already be accessible within the workspace. The blast radius is limited to information disclosure of job run details, which is a low-severity risk in most security contexts.
From the tool's definition Tool name 'get-job-runs' and description 'Get recent job runs by job id' indicate a retrieval operation. The verb 'Get' and action of fetching historical job run data are consistent with read-only operations.
Documented attack patterns abuse exactly the kind of access get-job-runs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Databricks Unity Catalog MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-job-runs:
{
"version": "1",
"default": "deny",
"tools": {
"get-job-runs": {}
}
} get-job-runs 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.
Get recent job runs by job id. It is categorised as a Read tool in the Databricks Unity Catalog MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Databricks Unity Catalog MCP Server MCP server in PolicyLayer and add a rule for get-job-runs: 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 Unity Catalog MCP Server. Nothing to install.
get-job-runs 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-runs 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-runs. 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-runs is provided by the Databricks Unity Catalog MCP Server MCP server (revodatanl/databricks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Databricks Unity Catalog MCP Server, 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.
8 Databricks Unity Catalog MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.