Generate data visualizations from JSON data with automatic chart type selection, analysis, and multiple output formats (HTML, PNG, Word)
AI agents use generate_visualization to create or update resources in Watsonx Visualization MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Watsonx Visualization MCP Server environment.
This tool creates new data artifacts (visualization files) in multiple output formats, which constitutes a Write operation. It doesn't retrieve existing data (Read), execute arbitrary code (Execute), delete anything (Destructive), or move money (Financial). Severity is medium because misuse could create misleading visualizations or consume storage/resources, but the effects are reversible.
From the tool's definition Tool generates visualizations and outputs them in multiple formats (HTML, PNG, Word), creating new files/artifacts. Description states it will 'generate' visualizations and produce 'output formats', indicating file creation or data modification.
Attacks that exploit this kind of access
Generate data visualizations from JSON data with automatic chart type selection, analysis, and multiple output formats (HTML, PNG, Word). It is categorised as a Write tool in the Watsonx Visualization MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Watsonx Visualization MCP Server MCP server in PolicyLayer and add a rule for generate_visualization: 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 Watsonx Visualization MCP Server. Nothing to install.
generate_visualization 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 generate_visualization 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 generate_visualization. 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.
generate_visualization is provided by the Watsonx Visualization MCP Server MCP server (tdognin/watsonx-visualization-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 →