list_loki_label_names

Lists all available label names (keys) found in logs within a specified Loki datasource and time range

SERVERGrafana MCP Server SOURCE0xteamhq/mcp-grafana

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/0xteamhq-mcp-grafana/list-loki-label-names.md

WHAT IT DOES

What list_loki_label_names does on Grafana MCP Server

AI agents call list_loki_label_names to retrieve information from Grafana MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_loki_label_names is rated Low

This tool retrieves metadata (label keys) from a Loki datasource without altering data or triggering side effects. It is a straightforward read operation analogous to schema introspection or list operations. The low severity reflects minimal blast radius—discovering available labels poses no direct risk even if misused.

From the tool's definition Tool 'lists all available label names' in logs—a read-only query operation with no modification, deletion, or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_loki_label_names safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Grafana MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_loki_label_names, this is the rule to start with:

list_loki_label_names Allowed

list_loki_label_names is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_loki_label_names": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Grafana MCP Server, apply this rule, and every list_loki_label_names call is checked against it from then on.

FAQ

Questions about list_loki_label_names

What does the list_loki_label_names tool do? +

Lists all available label names (keys) found in logs within a specified Loki datasource and time range. It is categorised as a Read tool in the Grafana MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_loki_label_names? +

Register the Grafana MCP Server MCP server in PolicyLayer and add a rule for list_loki_label_names: 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 Grafana MCP Server. Nothing to install.

What risk level is list_loki_label_names? +

list_loki_label_names is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_loki_label_names? +

Yes. Add a rate_limit block to the list_loki_label_names 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.

How do I block list_loki_label_names completely? +

Set action: deny in the PolicyLayer policy for list_loki_label_names. 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.

What MCP server provides list_loki_label_names? +

list_loki_label_names is provided by the Grafana MCP Server MCP server (0xteamhq/mcp-grafana). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Grafana MCP Server, and thousands of servers like it.

This server

All 43 Grafana MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →