List all Steampipe plugins installed on the system. Plugins provide access to different data sources like AWS, GCP, or Azure.
AI agents call steampipe_plugin_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 retrieves metadata about installed plugins without retrieving sensitive data, executing code, or modifying system state. It is informational only, making it a Read category tool with low severity. The blast radius of misuse is minimal — an AI agent learning what plugins are available poses no immediate operational risk.
From the tool's definition Tool performs 'List all Steampipe plugins installed on the system' — a query/enumeration operation with no modification or execution of external operations.
Documented attack patterns abuse exactly the kind of access steampipe_plugin_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_plugin_list:
{
"version": "1",
"default": "deny",
"tools": {
"steampipe_plugin_list": {}
}
}steampipe_plugin_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 Steampipe plugins installed on the system. Plugins provide access to different data sources like AWS, GCP, or Azure. 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_plugin_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_plugin_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_plugin_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_plugin_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_plugin_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.