This record as markdown: /tools/54yyyu-kaggle-mcp/kernel-pull.md
What kernel_pull does on Kaggle-MCP
AI agents call kernel_pull 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 kernel_pull is rated Low
Without an explicit description, classification relies on naming convention and context. 'Pull' typically indicates retrieval rather than modification or execution. The Kaggle kernel context suggests downloading or fetching notebook/script content, which is a read operation. Confidence is moderate (0.7) due to empty description; if 'kernel_pull' actually executes kernels, it would be Execute instead.
From the tool's definition Tool name 'kernel_pull' suggests retrieving or downloading kernel code/data from Kaggle. The method naming pattern 'pull' is consistent with fetching operations.
Attacks that exploit this kind of access
The rule that runs kernel_pull 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 kernel_pull, this is the rule to start with:
kernel_pull 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 kernel_pull call is checked against it from then on.
Questions about kernel_pull
kernel_pull 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 kernel_pull: 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.
kernel_pull 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 kernel_pull 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 kernel_pull. 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.
kernel_pull 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