Low Risk

get_dashboard_by_uid

Retrieves the complete dashboard, including panels, variables, and settings, for a specific dashboard identified by its UID. WARNING: Large dashboards can consume significant context window space. Consider using get_dashboard_summary for overview or get_dashboard_property for specific data instead.

Single-target operation

Part of the Mcp Grafana Npx MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call get_dashboard_by_uid to retrieve information from Mcp Grafana Npx without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_dashboard_by_uid only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

mcp-grafana-npx.yaml
tools:
  get_dashboard_by_uid:
    rules:
      - action: allow

See the full Mcp Grafana Npx policy for all 50 tools.

Tool Name get_dashboard_by_uid
Category Read
Risk Level Low

View all 50 tools →

Agents calling read-class tools like get_dashboard_by_uid have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get_dashboard_by_uid tool do? +

Retrieves the complete dashboard, including panels, variables, and settings, for a specific dashboard identified by its UID. WARNING: Large dashboards can consume significant context window space. Consider using get_dashboard_summary for overview or get_dashboard_property for specific data instead.. It is categorised as a Read tool in the Mcp Grafana Npx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dashboard_by_uid? +

Add a rule in your Intercept YAML policy under the tools section for get_dashboard_by_uid. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Grafana Npx MCP server.

What risk level is get_dashboard_by_uid? +

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

Can I rate-limit get_dashboard_by_uid? +

Yes. Add a rate_limit block to the get_dashboard_by_uid rule in your Intercept 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 get_dashboard_by_uid completely? +

Set action: deny in the Intercept policy for get_dashboard_by_uid. 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 get_dashboard_by_uid? +

get_dashboard_by_uid is provided by the Mcp Grafana Npx MCP server (mcp-grafana-npx). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mcp Grafana Npx

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.