Low Risk

list_projects

Read-only. Use when the target project is unknown or the user names a project instead of providing an id. Returns accessible Dreamlit projects in the approved workspace with project and workflow-list URLs. Do not use to inspect workflow structure or author changes.

Part of the Dreamlit server.

list_projects is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DREAMLIT →

Free to start. No card required.

AI agents call list_projects to retrieve information from Dreamlit without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_projects only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full Dreamlit policy for all 11 tools.

Get this rule live on your own Dreamlit server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DREAMLIT →

View all 11 tools →

These attack patterns abuse exactly the kind of access list_projects gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so list_projects only ever does what you allow.

SECURE DREAMLIT →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the list_projects tool do? +

Read-only. Use when the target project is unknown or the user names a project instead of providing an id. Returns accessible Dreamlit projects in the approved workspace with project and workflow-list URLs. Do not use to inspect workflow structure or author changes.. It is categorised as a Read tool in the Dreamlit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_projects? +

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

What risk level is list_projects? +

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

Can I rate-limit list_projects? +

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

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

list_projects is provided by the Dreamlit MCP server (https://mcp.dreamlit.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dreamlit tool call.

Deterministic rules across all 11 Dreamlit tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.