list_teams
Search for Grafana teams by a query string. Returns a list of matching teams with details
This record as markdown: /tools/0xteamhq-mcp-grafana/list-teams.md
What list_teams does on Grafana MCP Server
AI agents call list_teams 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.
Why list_teams is rated Low
This tool retrieves and returns information about teams in Grafana. It performs a search operation that queries existing data without creating, modifying, deleting, or executing any actions. The blast radius is minimal—reading team membership lists poses low risk unless exposed teams are sensitive, but the tool itself is fundamentally a read-only query operation.
From the tool's definition Tool name is 'list_teams' and description states it 'Search for Grafana teams by a query string. Returns a list of matching teams with details' — pure data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_teams 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_teams, this is the rule to start with:
list_teams is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Grafana MCP Server, apply this rule, and every list_teams call is checked against it from then on.
Questions about list_teams
Search for Grafana teams by a query string. Returns a list of matching teams with details. It is categorised as a Read tool in the Grafana MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Grafana MCP Server MCP server in PolicyLayer and add a rule for list_teams: 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.
list_teams 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_teams 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_teams. 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_teams 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.
More on Grafana MCP Server, and thousands of servers like it.
This server
Across the catalogue