Critical Risk →

remove_user_from_group

remove_user_from_group

How to control remove_user_from_group ↓

What remove_user_from_group does on Prometheus MCP Server

AI agents call remove_user_from_group 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.

Critical Risk

Why remove_user_from_group needs a policy

The name strongly implies removing a user from a group, which is a destructive/irreversible IAM/identity operation that revokes access. This cannot typically be undone automatically and could impact user permissions significantly. Confidence is reduced due to the empty description, but the naming convention is clear enough to suggest a destructive access-control change.

From the tool's definition Tool name 'remove_user_from_group' — no description provided.

Documented attack patterns abuse exactly the kind of access remove_user_from_group gives an agent:

How to control remove_user_from_group

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 remove_user_from_group:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_user_from_group"
  ]
}

remove_user_from_group disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Prometheus MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about remove_user_from_group

What does the remove_user_from_group tool do? +

remove_user_from_group. 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.

How do I enforce a policy on remove_user_from_group? +

Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for remove_user_from_group: 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.

What risk level is remove_user_from_group? +

remove_user_from_group is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_user_from_group? +

Yes. Add a rate_limit block to the remove_user_from_group 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.

How do I block remove_user_from_group completely? +

Set action: deny in the PolicyLayer policy for remove_user_from_group. 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.

What MCP server provides remove_user_from_group? +

remove_user_from_group 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.

Enforce policy on every Prometheus MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.