AI agents call list_tables_in_schema to retrieve information from Redshift MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves database metadata (table names within a schema) without modifying data or executing arbitrary operations. It is a read-only introspection function typical of database exploration tools. While the description is empty, the name is unambiguous and the context from sibling tools reinforces this classification.
From the tool's definition Tool name 'list_tables_in_schema' combined with sibling tool patterns ('list_schemas', 'explain_query') and server description indicating 'schema exploration' indicates retrieval of metadata. No destructive, write, or execute operations implied.
Documented attack patterns abuse exactly the kind of access list_tables_in_schema gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Redshift MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_tables_in_schema:
{
"version": "1",
"default": "deny",
"tools": {
"list_tables_in_schema": {}
}
}list_tables_in_schema is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_tables_in_schema. It is categorised as a Read tool in the Redshift MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Redshift MCP Server MCP server in PolicyLayer and add a rule for list_tables_in_schema: 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 Redshift MCP Server. Nothing to install.
list_tables_in_schema is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_tables_in_schema 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.
Set action: deny in the PolicyLayer policy for list_tables_in_schema. 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.
list_tables_in_schema is provided by the Redshift MCP Server MCP server (tuanknguyen/redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Redshift 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.
5 Redshift MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.