Manage Grafana datasources.
AI agents use manage_grafana_datasources to create or update resources in Observability MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Observability MCP Server environment.
Managing datasources involves creating, updating, or modifying configurations that feed monitoring data into Grafana. This is a Write operation—it alters system configuration state reversibly.
From the tool's definition Tool name 'manage_grafana_datasources' and description 'Manage Grafana datasources' indicate operations to create, update, or modify datasource configurations in Grafana.
Attacks that exploit this kind of access
Manage Grafana datasources. It is categorised as a Write tool in the Observability MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Observability MCP Server MCP server in PolicyLayer and add a rule for manage_grafana_datasources: 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 Observability MCP Server. Nothing to install.
manage_grafana_datasources is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_grafana_datasources 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 manage_grafana_datasources. 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.
manage_grafana_datasources is provided by the Observability MCP Server MCP server (sandraschi/observability-mcp). 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 →