List files in a CML project at the specified path.
AI agents call list_files 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.
This tool only retrieves and lists file metadata from a CML project directory. It has no side effects, cannot modify data, execute code, or trigger external operations. The blast radius of misuse is minimal—an agent could only view files they already have access to within the project scope.
From the tool's definition Tool name is 'list_files' and description states it 'List files in a CML project at the specified path' - a pure retrieval operation with no modification or execution capabilities.
Attacks that exploit this kind of access
List files in a CML project at the specified path. 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_files: 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_files 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_files 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_files. 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_files 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 →