lightdash_get_catalog

THE RISK

Low Risk

Why lightdash_get_catalog needs a policy

This tool retrieves catalog metadata for a Lightdash project without any side effects, creation, modification, deletion, or execution of code. It is a straightforward query operation that matches the 'Read' category definition of retrieving or querying data with no side effects.

From the tool's definition Tool name 'lightdash_get_catalog' and description 'Get catalog for a project' indicate data retrieval. The server description confirms this MCP server 'provides tools to list and retrieve projects, spaces, charts, dashboards, and metrics' with no mention of…

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

POLICY

How to control lightdash_get_catalog

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

policy.json

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

lightdash_get_catalog 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 Lightdash 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 Lightdash MCP Server tools

Read lightdash_get_analytics Get analytics for a specific table in the data catalog Read lightdash_get_charts_as_code Get charts as code for a project Read lightdash_get_custom_metrics Get custom metrics for a project Read lightdash_get_dashboards_as_code Get dashboards as code for a project Read lightdash_get_metadata Get metadata for a specific table in the data catalog Read lightdash_get_metrics_catalog Get metrics catalog for a project Read lightdash_get_project Get details of a specific project Read lightdash_get_user_attributes Get organization user attributes

All 13 Lightdash 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 lightdash_get_catalog

What does the lightdash_get_catalog tool do? +

Get catalog for a project. It is categorised as a Read tool in the Lightdash MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lightdash_get_catalog? +

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

What risk level is lightdash_get_catalog? +

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

Can I rate-limit lightdash_get_catalog? +

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

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

lightdash_get_catalog is provided by the Lightdash MCP Server MCP server (syucream/lightdash-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Lightdash MCP Server tool call.

Start from Lightdash 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 →