View current Kaggle API configuration values.
AI agents call config_view to retrieve information from Kaggle-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only displays existing configuration settings. It has no capability to modify settings, execute commands, delete data, or affect external systems. The blast radius of misuse is minimal — an agent could only learn what configuration is already set (API credentials, paths, etc.), which is informational exposure rather than actionable harm. Classified as Read with low severity.
From the tool's definition Tool name is 'config_view' and description states 'View current Kaggle API configuration values' — a read-only operation that retrieves configuration data without modification or side effects.
Attacks that exploit this kind of access
View current Kaggle API configuration values. 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 config_view: 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.
config_view 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 config_view 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 config_view. 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.
config_view 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.
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 →