List all tables in the database with their schemas
AI agents call list_tables to retrieve information from Google Services 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 information about database structure (table names and schemas) with no side effects. It is a straightforward Read operation that poses minimal risk—an agent could discover what data exists but cannot access, modify, or delete it. The low severity reflects the limited blast radius of listing table metadata.
From the tool's definition Tool name 'list_tables' and description 'List all tables in the database with their schemas' indicate a query operation that retrieves metadata without modifying or executing operations.
Attacks that exploit this kind of access
List all tables in the database with their schemas. It is categorised as a Read tool in the Google Services MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Services MCP Server 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 Google Services MCP Server. 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 Google Services MCP Server MCP server (t4nm4ymittal/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →