AI agents use update_agent_runtime 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 verb 'update' indicates reversible modification of data or state rather than read-only retrieval or destructive deletion. Without a description, confidence is reduced, but the naming pattern and context among other AWS management tools suggests Write-category functionality.
From the tool's definition Tool name 'update_agent_runtime' suggests modification of agent runtime configuration or state. The empty description and presence among AWS-related tools (add_inline_policy, add_user_to_group, aggregate) indicate this is likely a Write operation that…
Documented attack patterns abuse exactly the kind of access update_agent_runtime 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 update_agent_runtime:
{
"version": "1",
"default": "deny",
"tools": {
"update_agent_runtime": {
"limits": [
{
"counter": "update_agent_runtime_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_agent_runtime 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.
update_agent_runtime. 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 update_agent_runtime: 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.
update_agent_runtime 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 update_agent_runtime 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 update_agent_runtime. 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.
update_agent_runtime 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.