Browse and list available DuckDB database files in a directory
AI agents call browse_databases to retrieve information from MCP Data Visualization Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only enumerates available database files in a directory—a passive information-gathering operation with no side effects, no code execution, and no data modification. It poses minimal risk as it cannot alter state or trigger operations beyond directory listing.
From the tool's definition Tool name 'browse_databases' and description 'Browse and list available DuckDB database files in a directory' indicate a read-only operation that retrieves or queries information without modifying data or triggering external operations.
Documented attack patterns abuse exactly the kind of access browse_databases gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Data Visualization Server, and nothing reaches the server without passing your rules. This is the rule we recommend for browse_databases:
{
"version": "1",
"default": "deny",
"tools": {
"browse_databases": {}
}
} browse_databases is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Browse and list available DuckDB database files in a directory. It is categorised as a Read tool in the MCP Data Visualization Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Data Visualization Server MCP server in PolicyLayer and add a rule for browse_databases: 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 Data Visualization Server. Nothing to install.
browse_databases is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the browse_databases 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 browse_databases. 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.
browse_databases is provided by the MCP Data Visualization Server MCP server (xoniks/mcp-visualization-duckdb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Data Visualization Server, 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.
28 MCP Data Visualization Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.