AI agents call detach_group_policy to permanently remove resources in Prometheus MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Detaching a group policy removes IAM permissions from a group of users, which is a significant and potentially irreversible security action (the policy linkage is severed). While the policy itself is not deleted, removing access controls can have severe security implications. The description is empty, lowering confidence, but the name strongly implies an IAM policy detachment operation.
From the tool's definition Tool name 'detach_group_policy' — 'detach' implies removing a policy association from a group, which is an IAM permission change that removes access controls.
Documented attack patterns abuse exactly the kind of access detach_group_policy 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 detach_group_policy:
{
"version": "1",
"default": "deny",
"hide": [
"detach_group_policy"
]
}detach_group_policy disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
detach_group_policy. It is categorised as a Destructive tool in the Prometheus MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for detach_group_policy: 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.
detach_group_policy is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the detach_group_policy 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 detach_group_policy. 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.
detach_group_policy 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.