List all available Steampipe tables. Use schema and filter parameters to narrow down results.
AI agents call steampipe_table_list to retrieve information from Steampipe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves and lists available table metadata. The parameters (schema, filter) are used for narrowing results, not modifying state. The blast radius is minimal—an AI agent cannot cause harm by listing tables, as this is informational retrieval only.
From the tool's definition Tool name 'steampipe_table_list' and description 'List all available Steampipe tables' indicate retrieval of metadata with optional filtering via schema and filter parameters.
Documented attack patterns abuse exactly the kind of access steampipe_table_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Steampipe, and nothing reaches the server without passing your rules. This is the rule we recommend for steampipe_table_list:
{
"version": "1",
"default": "deny",
"tools": {
"steampipe_table_list": {}
}
}steampipe_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 Steampipe tables. Use schema and filter parameters to narrow down results. It is categorised as a Read tool in the Steampipe MCP Server, which means it retrieves data without modifying state.
Register the Steampipe MCP server in PolicyLayer and add a rule for steampipe_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 Steampipe. Nothing to install.
steampipe_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 steampipe_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 steampipe_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.
steampipe_table_list is provided by the Steampipe MCP server (turbot/steampipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Steampipe tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Steampipe tools catalogued and risk-classified — across an index of 42,500+ MCP servers.