Retrieves detailed information about a specific datasource using its name.
AI agents call get_datasource_by_name to retrieve information from Mcp Grafana without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves datasource configuration information without modifying, deleting, or executing any operations. It is a straightforward read operation that queries datasource metadata. The blast radius is minimal—an AI agent could learn details about datasources but cannot cause harm through retrieval alone.
From the tool's definition Tool name 'get_datasource_by_name' and description 'Retrieves detailed information about a specific datasource using its name' indicate a query/fetch operation with no side effects.
Attacks that exploit this kind of access
Retrieves detailed information about a specific datasource using its name. It is categorised as a Read tool in the Mcp Grafana MCP Server, which means it retrieves data without modifying state.
Register the Mcp Grafana 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 Mcp Grafana. Nothing to install.
get_datasource_by_name 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 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.
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.
get_datasource_by_name is provided by the Mcp Grafana MCP server (@leval/mcp-grafana). 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 →