Export the vector visualization as a standalone HTML file with modern UI. Automatically saves to file and returns the path. Includes embedded Plotly.js, interactive clusters, and gradient design.
AI agents use export_visualization_html to create or update resources in MCP Codebase Index — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Codebase Index environment.
This tool generates and persists data (an HTML visualization file) to the filesystem, making it a Write operation rather than Read (it creates new output) or Destructive (the file can be deleted or overwritten without permanent loss). The blast radius is minimal—a misused agent could create unwanted HTML files, wasting storage or cluttering the filesystem, but no critical data is at risk.
From the tool's definition The tool creates and writes a new file to disk ('Automatically saves to file and returns the path'), which is a reversible write operation. The output is a static HTML visualization file with no destructive or irreversible effects.
Documented attack patterns abuse exactly the kind of access export_visualization_html gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Codebase Index, and nothing reaches the server without passing your rules. This is the rule we recommend for export_visualization_html:
{
"version": "1",
"default": "deny",
"tools": {
"export_visualization_html": {
"limits": [
{
"counter": "export_visualization_html_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} export_visualization_html 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.
Free to start. No card required.
Export the vector visualization as a standalone HTML file with modern UI. Automatically saves to file and returns the path. Includes embedded Plotly.js, interactive clusters, and gradient design. It is categorised as a Write tool in the MCP Codebase Index MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Codebase Index MCP server in PolicyLayer and add a rule for export_visualization_html: 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 MCP Codebase Index. Nothing to install.
export_visualization_html 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 export_visualization_html 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 export_visualization_html. 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.
export_visualization_html is provided by the MCP Codebase Index MCP server (ngotaico/mcp-codebase-index). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Codebase Index, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 MCP Codebase Index tools catalogued and risk-classified — across an index of 43,000+ MCP servers.