This record as markdown: /tools/mcp-dev/delete-member-group.md
What delete-member-group does on Mcp Dev
AI agents call delete-member-group to permanently remove resources in Mcp Dev, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete-member-group is rated Critical
This tool permanently removes a member group from the Umbraco CMS, which is an irreversible destructive action. Deletion cannot be undone without recovery mechanisms outside the tool. The blast radius depends on the member group's size and associated permissions, but the action itself is definitively destructive.
From the tool's definition Tool name is 'delete-member-group' and description states 'Deletes a member group by Id'. The verb 'Deletes' directly indicates an irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete-member-group safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-member-group, this is the rule to start with:
delete-member-group is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every delete-member-group call is checked against it from then on.
Questions about delete-member-group
Deletes a member group by Id. It is categorised as a Destructive tool in the Mcp Dev MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for delete-member-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 Mcp Dev. Nothing to install.
delete-member-group 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 delete-member-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.
Set action: deny in the PolicyLayer policy for delete-member-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.
delete-member-group is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
Across the catalogue