List all tables and views in a schema with estimated row counts.
AI agents call list-tables to retrieve information from Tusk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves database schema metadata (table and view names with row counts) without creating, modifying, deleting, or executing code. It is purely informational and has no side effects on the database or external systems. The read-only server design and metadata-listing nature confirm Read category with low severity due to minimal blast radius if misused.
From the tool's definition Tool description states 'List all tables and views in a schema' and the server is explicitly described as 'read-only PostgreSQL MCP server' that 'perform[s] schema introspection'. The action is to list/query metadata with no modification capability.
Documented attack patterns abuse exactly the kind of access list-tables gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tusk, and nothing reaches the server without passing your rules. This is the rule we recommend for list-tables:
{
"version": "1",
"default": "deny",
"tools": {
"list-tables": {}
}
}list-tables 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 all tables and views in a schema with estimated row counts. It is categorised as a Read tool in the Tusk MCP Server, which means it retrieves data without modifying state.
Register the Tusk MCP server in PolicyLayer and add a rule for list-tables: 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 Tusk. Nothing to install.
list-tables 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 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. 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 is provided by the Tusk MCP server (volveezz/tusk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tusk, 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.
4 Tusk tools catalogued and risk-classified — across an index of 43,000+ MCP servers.