visualize_database_relationships

THE RISK

Low Risk

Why visualize_database_relationships needs a policy

This tool only explores and visualizes existing database schema relationships. It retrieves and displays metadata without modifying or executing operations on the database. The visual representation is a read-only output derived from existing database structure, presenting no side effects or risk of data modification.

From the tool's definition Tool generates visual representations of existing database relationships. The description explicitly states it is a generative/visualization function ('Generate a visual representation') with no mention of creating, modifying, or deleting data.

Documented attack patterns abuse exactly the kind of access visualize_database_relationships gives an agent:

POLICY

How to control visualize_database_relationships

PolicyLayer is an MCP gateway — it sits between your AI agents and Metabase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for visualize_database_relationships:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "visualize_database_relationships": {}
  }
}

visualize_database_relationships is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Metabase MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Metabase MCP Server tools

Execute execute_action Execute a Metabase action with parameters Execute run_database_query Execute a SQL query against a database Read db_overview Get a high-level overview of all tables in a database Read get_action_details Get detailed information about a specific action Read get_database_metadata Get detailed metadata for a specific database Read list_actions List all actions configured in Metabase Read list_databases List all databases configured in Metabase Read table_detail Get detailed information about a specific table

All 9 Metabase MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about visualize_database_relationships

What does the visualize_database_relationships tool do? +

Generate a visual representation of database relationships. It is categorised as a Read tool in the Metabase MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on visualize_database_relationships? +

Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for visualize_database_relationships: 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 Metabase MCP Server. Nothing to install.

What risk level is visualize_database_relationships? +

visualize_database_relationships is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit visualize_database_relationships? +

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

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

visualize_database_relationships is provided by the Metabase MCP Server MCP server (sazboxai/mcp_metabase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Metabase MCP Server tool call.

Start from Metabase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →