Add a participant to a chat room.
AI agents use add_my_chat_participant to create or update resources in Thenvoi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Thenvoi MCP Server environment.
This tool creates or modifies chat room state by adding participants, which is reversible (participants can typically be removed). It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial).
From the tool's definition Tool name 'add_my_chat_participant' and description 'Add a participant to a chat room' indicate creation/modification of chat membership. The verb 'add' and action of modifying chat room composition are consistent with Write category operations.
Attacks that exploit this kind of access
Add a participant to a chat room. It is categorised as a Write tool in the Thenvoi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Thenvoi MCP Server MCP server in PolicyLayer and add a rule for add_my_chat_participant: 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 Thenvoi MCP Server. Nothing to install.
add_my_chat_participant 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 add_my_chat_participant 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 add_my_chat_participant. 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.
add_my_chat_participant is provided by the Thenvoi MCP Server MCP server (thenvoi/thenvoi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →