send_my_chat_message
AI agents use send_my_chat_message 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 and sends chat messages, which is a reversible data modification operation (messages can be deleted or edited). It does not execute arbitrary code, delete data irreversibly, or move money. The description is empty, reducing confidence slightly, but the tool name and server context make the Write category clear.
From the tool's definition Tool name 'send_my_chat_message' indicates creation of a new message in a chat context. Sibling tools include 'create_agent_chat_message' which confirms this server handles message creation.
Attacks that exploit this kind of access
send_my_chat_message. 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 send_my_chat_message: 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.
send_my_chat_message 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 send_my_chat_message 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 send_my_chat_message. 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.
send_my_chat_message 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 →