This record as markdown: /tools/54yyyu-kaggle-mcp/datasets-list.md
What datasets_list does on Kaggle-MCP
AI agents call datasets_list 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 datasets_list is rated Low
A 'list' operation by semantic convention retrieves and displays available datasets without creating, modifying, or deleting data. This is a read-only query operation with no side effects. While the description is empty (slightly reducing confidence from 0.99 to 0.95), the tool name combined with server context and sibling tool patterns makes the classification reliable.
From the tool's definition Tool name 'datasets_list' indicates a listing/enumeration function. The server description confirms this connects to Kaggle API for 'dataset' operations.
Attacks that exploit this kind of access
The rule that runs datasets_list 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 datasets_list, this is the rule to start with:
datasets_list 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 datasets_list call is checked against it from then on.
Questions about datasets_list
datasets_list is a read tool on the Kaggle MCP server. 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 datasets_list: 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.
datasets_list 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 datasets_list 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 datasets_list. 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.
datasets_list 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