Send a message to an existing Mesh Thread (group DM).
AI agents use send_mesh_message to create or update resources in MCP-Networkbot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Networkbot environment.
The tool creates/adds data (messages) to an existing conversation thread in a professional networking context. This is reversible (messages can typically be deleted or edited) and does not execute arbitrary code, delete data, or move money. Write category is appropriate.
From the tool's definition Tool description states it 'Send[s] a message to an existing Mesh Thread', which creates new message data in a group conversation. This is a write operation that modifies shared state by adding content to a thread.
Attacks that exploit this kind of access
Send a message to an existing Mesh Thread (group DM). It is categorised as a Write tool in the MCP-Networkbot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-Networkbot MCP server in PolicyLayer and add a rule for send_mesh_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 MCP-Networkbot. Nothing to install.
send_mesh_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_mesh_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_mesh_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_mesh_message is provided by the MCP-Networkbot MCP server (kunalkhanna2007-sys/networkbot-python). 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 →