get_datasource_by_name

Retrieves detailed information about a specific datasource using its name.

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/get-datasource-by-name.md

What get_datasource_by_name does on Grafana MCP Server

AI agents call get_datasource_by_name 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 get_datasource_by_name is rated Low

This tool queries and returns datasource metadata without side effects. No data is modified, created, deleted, or executed. The action is purely informational retrieval, fitting the Read category with low severity since misuse would only expose configuration details rather than cause system harm.

From the tool's definition Tool name is 'get_datasource_by_name' and description states it 'Retrieves detailed information about a specific datasource' — uses retrieval verb without any modification, creation, or deletion capability.

Questions about get_datasource_by_name

What does the get_datasource_by_name tool do? +

Retrieves detailed information about a specific datasource using its name. 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 get_datasource_by_name? +

Register the Grafana MCP Server MCP server in PolicyLayer and add a rule for get_datasource_by_name: 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 get_datasource_by_name? +

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

Can I rate-limit get_datasource_by_name? +

Yes. Add a rate_limit block to the get_datasource_by_name 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 get_datasource_by_name completely? +

Set action: deny in the PolicyLayer policy for get_datasource_by_name. 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_datasource_by_name? +

get_datasource_by_name 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Grafana MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.