List all namespaces that have logs in Loki.
AI agents call list_namespaces to retrieve information from Loki MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about available namespaces without creating, modifying, deleting, or executing anything. It is a simple enumeration operation that enables users to discover what namespaces exist in the cluster. The blast radius of misuse is minimal—an attacker could only learn about namespace structure, not access sensitive data directly or cause operational disruption.
From the tool's definition Tool name 'list_namespaces' and description 'List all namespaces that have logs in Loki' indicate a retrieval operation with no modification or execution. The verb 'List' is explicitly read-only.
Attacks that exploit this kind of access
List all namespaces that have logs in Loki. It is categorised as a Read tool in the Loki MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Loki MCP Server MCP server in PolicyLayer and add a rule for list_namespaces: 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 Loki MCP Server. Nothing to install.
list_namespaces 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_namespaces 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_namespaces. 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_namespaces is provided by the Loki MCP Server MCP server (mvs5465-test/loki-mcp-server). 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 →