New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_contact_group_members

Remove one or more contacts from a group.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/remove-contact-group-members.md

What remove_contact_group_members does on TrekMail MCP Server

AI agents call remove_contact_group_members to permanently remove resources in TrekMail MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove_contact_group_members is rated Critical

Removing contacts from a group destroys the membership relationship. Unlike soft modifications (update/edit), removal of group members is typically not reversible without manual re-addition, making this Destructive. The blast radius is medium since it affects contact group memberships but not the contacts or group themselves.

From the tool's definition 'Remove one or more contacts from a group' — removal of members from a group is an irreversible operation that deletes the association between contacts and the group.

Questions about remove_contact_group_members

What does the remove_contact_group_members tool do? +

Remove one or more contacts from a group. It is categorised as a Destructive tool in the TrekMail 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_contact_group_members? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for remove_contact_group_members: 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 TrekMail MCP Server. Nothing to install.

What risk level is remove_contact_group_members? +

remove_contact_group_members 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_contact_group_members? +

Yes. Add a rate_limit block to the remove_contact_group_members 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_contact_group_members completely? +

Set action: deny in the PolicyLayer policy for remove_contact_group_members. 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_contact_group_members? +

remove_contact_group_members is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on TrekMail MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of TrekMail MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.