AI agents use create_datasource to create or update resources in Prometheus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prometheus MCP Server environment.
The 'create' prefix indicates a Write operation (reversible creation/modification of data). Without an explicit description, confidence is moderate. Severity is medium because creating a datasource in Prometheus could alter monitoring configuration and potentially affect alerting/observability, but it is not destructive (can be deleted) nor financial. The lack of description prevents higher confidence assessment.
From the tool's definition Tool name 'create_datasource' indicates creation of a data source. No description provided, but 'create' semantics in AWS Managed Prometheus context implies adding a new datasource configuration that can be modified or removed later.
Documented attack patterns abuse exactly the kind of access create_datasource gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_datasource:
{
"version": "1",
"default": "deny",
"tools": {
"create_datasource": {
"limits": [
{
"counter": "create_datasource_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_datasource stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_datasource. It is categorised as a Write tool in the Prometheus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for create_datasource: 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 Prometheus MCP Server. Nothing to install.
create_datasource 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 create_datasource 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 create_datasource. 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.
create_datasource is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Prometheus MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Prometheus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.