AI agents use create_access_key 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.
Creating an access key generates a new credential that grants programmatic API access to AWS resources. This is a reversible write operation—keys can be deactivated or deleted. However, the blast radius is significant: a compromised access key enables unauthorized AWS API calls affecting all resources the key's principal can access. The high severity reflects this risk despite the write classification.
From the tool's definition Tool name is 'create_access_key' with empty description; 'create' indicates data creation (reversible write operation). The name strongly suggests creating AWS access credentials.
Documented attack patterns abuse exactly the kind of access create_access_key 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_access_key:
{
"version": "1",
"default": "deny",
"tools": {
"create_access_key": {
"limits": [
{
"counter": "create_access_key_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_access_key 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_access_key. 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_access_key: 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_access_key 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_access_key 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_access_key. 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_access_key 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.