This record as markdown: /tools/54yyyu-kaggle-mcp/competition-list-files.md
What competition_list_files does on Kaggle-MCP
AI agents call competition_list_files to retrieve information from Kaggle-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why competition_list_files is rated Low
This tool retrieves and lists files within a competition context. The verb 'list' is a read-only operation that has no side effects, does not execute code, does not modify data, and does not delete or move resources. It simply returns information about existing competition files to the user.
From the tool's definition Tool name 'competition_list_files' and description 'List files in a competition' indicate a query/retrieval operation with no modification or execution of code.
Attacks that exploit this kind of access
The rule that runs competition_list_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kaggle-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For competition_list_files, this is the rule to start with:
competition_list_files is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kaggle-MCP, apply this rule, and every competition_list_files call is checked against it from then on.
Questions about competition_list_files
List files in a competition. It is categorised as a Read tool in the Kaggle-MCP MCP Server, which means it retrieves data without modifying state.
Register the Kaggle MCP server in PolicyLayer and add a rule for competition_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 Kaggle-MCP. Nothing to install.
competition_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 competition_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 competition_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.
competition_list_files is provided by the Kaggle MCP server (54yyyu/kaggle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kaggle, and thousands of servers like it.
This server
Across the catalogue