assign_tag_to_recipients
Assign a tag to multiple recipients (contacts)
This record as markdown: /tools/instantkom-mcp-server/assign-tag-to-recipients.md
What assign_tag_to_recipients does on instantKOM MCP Server
AI agents use assign_tag_to_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 assign_tag_to_recipients is rated Medium
The tool writes/modifies contact records by adding tags, which is reversible (tags can be removed). This falls under Write rather than Execute because it performs a structured data modification without triggering external operations or code execution.
From the tool's definition Tool assigns/modifies tags on multiple recipient contacts ('Assign a tag to multiple recipients'). This is a create/modify operation affecting contact metadata.
Attacks that exploit this kind of access
The rule that runs assign_tag_to_recipients safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For assign_tag_to_recipients, this is the rule to start with:
assign_tag_to_recipients stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every assign_tag_to_recipients call is checked against it from then on.
Questions about assign_tag_to_recipients
Assign a tag to 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.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for assign_tag_to_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.
assign_tag_to_recipients is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the assign_tag_to_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.
Set action: deny in the PolicyLayer policy for assign_tag_to_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.
assign_tag_to_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.
This server
Across the catalogue