config_unset

Clear a Kaggle API configuration value.

Server Kaggle-MCP realbytecode/kaggle-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What config_unset does on Kaggle-MCP

AI agents call config_unset to permanently remove resources in Kaggle-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why config_unset needs a policy

Clearing (unsetting) a configuration value is an irreversible removal of stored configuration data. Unlike an update/set operation, 'unset' removes the value entirely, which could disrupt authentication or API connectivity. This maps to Destructive since the configuration value is permanently removed rather than modified reversibly.

From the tool's definition Clear a Kaggle API configuration value

Questions about config_unset

What does the config_unset tool do? +

Clear a Kaggle API configuration value. It is categorised as a Destructive tool in the Kaggle-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on config_unset? +

Register the Kaggle- MCP server in PolicyLayer and add a rule for config_unset: 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_unset? +

config_unset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit config_unset? +

Yes. Add a rate_limit block to the config_unset 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_unset completely? +

Set action: deny in the PolicyLayer policy for config_unset. 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_unset? +

config_unset is provided by the Kaggle- MCP server (realbytecode/kaggle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.