run_extract · Cloudera Data Visualization MCP Server MCP

WHAT IT DOES

What run_extract does on Cloudera Data Visualization MCP Server

AI agents invoke run_extract to trigger actions in Cloudera Data Visualization MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_extract needs a policy

This tool triggers the execution of extract jobs in Cloudera Data Visualization, which are external operations that perform data extraction and processing. The effects depend on which job IDs are specified. While not destructive (data is not permanently deleted) nor financial, it executes operations whose consequences vary by input parameters.

From the tool's definition Tool description states 'Run one or more CDV data extract jobs' - the verb 'run' indicates execution of external operations (data extract jobs).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_extract Rate-limited

run_extract stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_extract": {
      "limits": [
        {
          "counter": "run_extract_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 run_extract

What does the run_extract tool do? +

Run one or more CDV data extract jobs by their comma-separated IDs. It is categorised as a Execute tool in the Cloudera Data Visualization MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_extract? +

Register the Cloudera Data Visualization MCP Server MCP server in PolicyLayer and add a rule for run_extract: 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 run_extract? +

run_extract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_extract? +

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

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

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