Update an existing CDV segment by its numeric ID.
AI agents use update_segment 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.
The tool updates an existing segment in Cloudera Data Visualization, which is a reversible write operation. While segments may be used for data filtering/segmentation in reports, updating them does not permanently delete data or execute arbitrary code.
From the tool's definition Tool name 'update_segment' and description 'Update an existing CDV segment' indicate modification of data that can be reversed by updating again or restoring from backups.
Attacks that exploit this kind of access
Update an existing CDV segment by its numeric ID. 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.
Register the Cloudera Data Visualization MCP Server MCP server in PolicyLayer and add a rule for update_segment: 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.
update_segment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_segment 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 update_segment. 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.
update_segment 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.
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 →