Lists the names of all Storage Insights dataset configurations for a given project.
AI agents call list_insights_configs to retrieve information from Observability without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing Storage Insights dataset configuration metadata for a given project without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk if accessed by an AI agent, as it only exposes non-sensitive configuration names.
From the tool's definition Tool name contains 'list' and description states 'Lists the names of all Storage Insights dataset configurations'. The verb 'list' and the action of retrieving configuration names without modification indicates a read-only query operation.
Attacks that exploit this kind of access
Lists the names of all Storage Insights dataset configurations for a given project. It is categorised as a Read tool in the Observability MCP Server, which means it retrieves data without modifying state.
Register the Observability MCP server in PolicyLayer and add a rule for list_insights_configs: 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 Observability. Nothing to install.
list_insights_configs 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_insights_configs 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_insights_configs. 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_insights_configs is provided by the Observability MCP server (@google-cloud/observability-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 →