remove_tag_from_recipients

Remove a tag from multiple recipients (contacts)

SERVERinstantKOM MCP Server SOURCEinstantkom/mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/instantkom-mcp-server/remove-tag-from-recipients.md

What remove_tag_from_recipients does on instantKOM MCP Server

AI agents use remove_tag_from_recipients to create or update resources in instantKOM MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your instantKOM MCP Server environment.

Why remove_tag_from_recipients is rated Medium

Removing a tag from contacts is a Write operation as it modifies data (tag associations) but is reversible - the tag can be re-added. The blast radius is medium since it affects multiple recipients but doesn't delete contacts or irreversible data.

From the tool's definition 'Remove a tag from multiple recipients (contacts)' - removes a tag association from contacts, which is a reversible modification

Questions about remove_tag_from_recipients

What does the remove_tag_from_recipients tool do? +

Remove a tag from multiple recipients (contacts). It is categorised as a Write tool in the instantKOM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remove_tag_from_recipients? +

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

What risk level is remove_tag_from_recipients? +

remove_tag_from_recipients is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit remove_tag_from_recipients? +

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

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

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

More on instantKOM 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 instantKOM 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.