databricks_log_param

A write tool on the Databricks MCP server.

SERVERDatabricks MCP Server SOURCEpypi:databricks-sdk-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/io-github-pramodbhatofficial-databricks-sdk-mcp/databricks-log-param.md

What databricks_log_param does on Databricks MCP Server

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

Why databricks_log_param is rated Medium

The name implies writing/recording a parameter value to some tracking store (likely MLflow experiment runs in Databricks). This is a Write operation as it creates or modifies data. Confidence is low due to empty description.

From the tool's definition Tool name 'databricks_log_param' suggests logging/recording a parameter value, likely in an experiment or run context (e.g., MLflow). No description provided.

Questions about databricks_log_param

What does the databricks_log_param tool do? +

databricks_log_param is a write tool on the Databricks MCP Server MCP server. It is categorised as a Write tool in the Databricks MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on databricks_log_param? +

Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for databricks_log_param: 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 Databricks MCP Server. Nothing to install.

What risk level is databricks_log_param? +

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

Can I rate-limit databricks_log_param? +

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

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

databricks_log_param is provided by the Databricks MCP Server MCP server (pypi:databricks-sdk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Databricks MCP Server, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Databricks MCP Server's. Pull the full record:

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.