Purpose: List all tables in the configured RawTree database with row and byte counts. NOT for: Reading table rows. Use run-query for data and describe-table for columns. Returns: Tables plus database and organization context. When to use: - User asks what data exists - You need a table name befor...
AI agents call list-tables to retrieve information from RawTree MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
list-tables retrieves and queries metadata about available tables (names, row counts, byte counts) without modifying data or triggering external operations. It is a read-only discovery/introspection tool. Low severity because exposure of table names and aggregate statistics poses minimal risk compared to actual data access or destructive operations.
From the tool's definition Tool description explicitly states it 'List[s] all tables in the configured RawTree database with row and byte counts' and returns 'Tables plus database and organization context.' The description clarifies it is 'NOT for: Reading table rows' and directs users…
Attacks that exploit this kind of access
Purpose: List all tables in the configured RawTree database with row and byte counts. NOT for: Reading table rows. Use run-query for data and describe-table for columns. Returns: Tables plus database and organization context. When to use: - User asks what data exists - You need a table name before querying - You want to verify that an insert auto-created a table. It is categorised as a Read tool in the RawTree MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RawTree 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 RawTree 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 RawTree MCP Server MCP server (rawtreedb/rawtree-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 →