list_job_runs
AI agents call list_job_runs to retrieve information from Cloudera Machine Learning (CML) MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or enumerates job run records without modifying data or triggering actions. The 'list_' prefix is a standard pattern for read-only queries. No side effects or state changes are implied. Confidence is slightly reduced due to missing description, but sibling tools with similar names (list_jobs, list_files) are clearly Read operations.
From the tool's definition Tool name 'list_job_runs' indicates a listing/querying operation. The 'list_*' pattern is consistent with other Read tools on this server (list_files, list_jobs, list_projects, list_runtime_addons).
Attacks that exploit this kind of access
list_job_runs. It is categorised as a Read tool in the Cloudera Machine Learning (CML) MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cloudera Machine Learning (CML) MCP Server MCP server in PolicyLayer and add a rule for list_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 Cloudera Machine Learning (CML) MCP Server. Nothing to install.
list_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 list_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 list_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.
list_job_runs is provided by the Cloudera Machine Learning (CML) MCP Server MCP server (yw449/cloudera-cml-mcp-server). 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 →