set_log_level · Cloudera Data Visualization MCP Server MCP

WHAT IT DOES

What set_log_level does on Cloudera Data Visualization MCP Server

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

WHY IT NEEDS A POLICY

Why set_log_level needs a policy

This tool modifies system configuration (log level) which is a reversible write operation. While it doesn't create or delete data, it changes system behavior and logging verbosity. The required 'sys_viewlogs' permission suggests administrative access. Severity is medium because misconfiguration could hide important security events or generate excessive logs, but the effect is reversible by setting it back.

From the tool's definition Tool description states 'Set the log level for the root logger' - a modification operation that changes system configuration state.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_log_level Rate-limited

set_log_level 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": {
    "set_log_level": {
      "limits": [
        {
          "counter": "set_log_level_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cloudera Data Visualization MCP Server, so you can run agents against it safely.

FAQ

Questions about set_log_level

What does the set_log_level tool do? +

Set the log level for the root logger. Requires sys_viewlogs permission. It is categorised as a Write tool in the Cloudera Data Visualization 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 set_log_level? +

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

What risk level is set_log_level? +

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

Can I rate-limit set_log_level? +

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

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

set_log_level is provided by the Cloudera Data Visualization MCP Server MCP server (kevintalbert/cdv-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.