Send a message in a chat conversation
AI agents use send_chat_message to create or update resources in VoIPBin MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VoIPBin MCP Server environment.
This is a Write operation because it creates new data (a chat message) in a persistent system. It has moderate severity because unauthorized sending of messages could enable impersonation, spam, or disclosure of sensitive information, but is not Destructive (messages can be deleted/edited), Financial, or Execute (no code/command execution).
From the tool's definition Tool description states 'Send a message in a chat conversation' — this creates/writes a new chat message, modifying the conversation history irreversibly from the recipient's perspective.
Attacks that exploit this kind of access
Send a message in a chat conversation. It is categorised as a Write tool in the VoIPBin MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VoIPBin MCP Server MCP server in PolicyLayer and add a rule for send_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 VoIPBin MCP Server. Nothing to install.
send_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_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_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_chat_message is provided by the VoIPBin MCP Server MCP server (nrjchnd/voipbin-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 →