Low Risk

lightdash_list_projects

List all projects in the Lightdash organization

How to control lightdash_list_projects ↓

What lightdash_list_projects does on Lightdash MCP Server

AI agents call lightdash_list_projects to retrieve information from Lightdash MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why lightdash_list_projects needs a policy

This tool retrieves and enumerates projects from Lightdash without modifying, executing, or deleting anything. It is a straightforward read operation. The severity is low because even if an AI agent misuses this tool, it can only access metadata about existing projects—no data modification or financial impact is possible.

From the tool's definition Tool name is 'lightdash_list_projects' and description states it 'List all projects in the Lightdash organization'. The verb 'list' and the read-only nature of retrieving a collection of projects indicates a query operation with no side effects.

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

How to control lightdash_list_projects

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_list_projects:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lightdash_list_projects": {}
  }
}

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

  1. Create a free account and register Lightdash MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about lightdash_list_projects

What does the lightdash_list_projects tool do? +

List all projects in the Lightdash organization. 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_list_projects? +

Register the Lightdash MCP Server MCP server in PolicyLayer and add a rule for lightdash_list_projects: 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_list_projects? +

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

Can I rate-limit lightdash_list_projects? +

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

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

lightdash_list_projects 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.

Free to start. No card required.

13 Lightdash MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.