list_databases

// WHEN AI AGENTS USE THIS TOOL

AI agents call list_databases to retrieve information from Amazon Redshift MCP Server 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.

// WHY ENFORCE A POLICY ON LIST_DATABASES

Even though list_databases 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.

// RECOMMENDED POLICY

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

amazon-redshift-mcp-server.yaml

tools:
  list_databases:
    rules:
      - action: allow

See the full Amazon Redshift MCP Server policy for all 6 tools.

// DETAILS

Tool Name list_databases

Category Read

MCP Server Amazon Redshift MCP Server MCP Server

Risk Level Low

// MORE AMAZON REDSHIFT MCP SERVER TOOLS

Execute execute_query Read list_clusters Read list_columns Read list_schemas Read list_tables

// WHAT CAN GO WRONG

Agents calling read-class tools like list_databases have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Firecrawl Web Scraping Server firecrawl_check_crawl_status Firecrawl Web Scraping Server firecrawl_crawl Firecrawl Web Scraping Server firecrawl_deep_research Firecrawl Web Scraping Server firecrawl_extract Firecrawl Web Scraping Server firecrawl_map Firecrawl Web Scraping Server firecrawl_scrape

// RELATED READING

// FAQ

What does the list_databases tool do? +

List all databases in a specified Amazon Redshift cluster. This tool queries the SVV_REDSHIFT_DATABASES system view to discover all databases that the user has access to in the specified cluster, including local databases and databases created from datashares. ## Usage Requirements - Ensure your AWS credentials are properly configured (via AWS_PROFILE or default credentials). - The cluster must be available and accessible. - Required IAM permissions: redshift-data:ExecuteStatement, redshift-data:DescribeStatement, redshift-data:GetStatementResult. - The user must have access to the specified database to query system views. ## Parameters - cluster_identifier: The unique identifier of the Redshift cluster to query. IMPORTANT: Use a valid cluster identifier from the list_clusters tool. - database_name: The database to connect to for querying system views (defaults to 'dev'). ## Response Structure Returns a list of RedshiftDatabase objects with the following structure: - database_name: The name of the database. - database_owner: The database owner user ID. - database_type: The type of database (local or shared). - database_acl: Access control information (for internal use). - database_options: The properties of the database. - database_isolation_level: The isolation level (Snapshot Isolation or Serializable). ## Usage Tips 1. First use list_clusters to get valid cluster identifiers. 2. Ensure the cluster status is 'available' before querying databases. 3. Use the default database name unless you know a specific database exists. 4. Note database types to understand if they are local or shared from datashares. ## Interpretation Best Practices 1. Focus on 'local' database types for cluster-native databases. 2. 'shared' database types indicate databases from datashares. 3. Use database names for subsequent schema and table discovery. 4. Consider database isolation levels for transaction planning.. It is categorised as a Read tool in the Amazon Redshift MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_databases? +

Add a rule in your Intercept YAML policy under the tools section for list_databases. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Amazon Redshift MCP Server MCP server.

What risk level is list_databases? +

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

Can I rate-limit list_databases? +

Yes. Add a rate_limit block to the list_databases rule in your Intercept 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_databases completely? +

Set action: deny in the Intercept policy for list_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.

What MCP server provides list_databases? +

list_databases is provided by the Amazon Redshift MCP Server MCP server (awslabs.redshift-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.