config_path

Set or view the path where files will be downloaded.

SERVERKaggle-MCP SOURCE54yyyu/kaggle-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/54yyyu-kaggle-mcp/config-path.md

WHAT IT DOES

What config_path does on Kaggle-MCP

AI agents use config_path to create or update resources in Kaggle-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kaggle-MCP environment.

RISK

Why config_path is rated Medium

This tool modifies configuration state (download path) reversibly. It does not execute code, delete data, or move money. While it can influence where downloads are stored, the change is easily reversible by setting a different path. Classified as Write rather than Read because the 'set' capability modifies persistent configuration, even though viewing is also supported.

From the tool's definition Tool description states 'Set or view the path where files will be downloaded' — 'set' indicates modification of configuration data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs config_path 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 config_path, this is the rule to start with:

config_path Rate-limited

config_path stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "config_path": {
      "limits": [
        {
          "counter": "config_path_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kaggle-MCP, apply this rule, and every config_path call is checked against it from then on.

FAQ

Questions about config_path

What does the config_path tool do? +

Set or view the path where files will be downloaded. It is categorised as a Write tool in the Kaggle-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on config_path? +

Register the Kaggle MCP server in PolicyLayer and add a rule for config_path: 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.

What risk level is config_path? +

config_path is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit config_path? +

Yes. Add a rate_limit block to the config_path 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.

How do I block config_path completely? +

Set action: deny in the PolicyLayer policy for config_path. 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.

What MCP server provides config_path? +

config_path 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.

KEEP EXPLORING

More on Kaggle, and thousands of servers like it.

This server

All 44 Kaggle tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →