List all available Tailpipe tables, including their schemas, descriptions, and column counts. Use tailpipe_table_show for detailed information about specific tables.
AI agents call tailpipe_table_list to retrieve information from Tailpipe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries table metadata (schemas, descriptions, column counts) without any side effects or data modification. It is purely informational and falls clearly under the 'Read' category. The severity is low because listing available tables poses minimal risk even if misused by an AI agent—it only exposes structural information without accessing actual log data or performing any operations.
From the tool's definition Tool description states 'List all available Tailpipe tables' with schemas and metadata. No modification, deletion, or execution capability described. This is a schema discovery/metadata retrieval operation.
Documented attack patterns abuse exactly the kind of access tailpipe_table_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tailpipe, and nothing reaches the server without passing your rules. This is the rule we recommend for tailpipe_table_list:
{
"version": "1",
"default": "deny",
"tools": {
"tailpipe_table_list": {}
}
} tailpipe_table_list 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 available Tailpipe tables, including their schemas, descriptions, and column counts. Use tailpipe_table_show for detailed information about specific tables. It is categorised as a Read tool in the Tailpipe MCP Server, which means it retrieves data without modifying state.
Register the Tailpipe MCP server in PolicyLayer and add a rule for tailpipe_table_list: 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 Tailpipe. Nothing to install.
tailpipe_table_list 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 tailpipe_table_list 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 tailpipe_table_list. 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.
tailpipe_table_list is provided by the Tailpipe MCP server (turbot/tailpipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tailpipe, 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.
10 Tailpipe tools catalogued and risk-classified — across an index of 43,000+ MCP servers.