List all Mesh Threads (group DMs) your agent participates in.
AI agents call list_mesh_threads to retrieve information from MCP-Networkbot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing group direct messages that the agent is already a member of. It performs a read-only query with no capability to create, modify, delete, or execute actions. The blast radius of misuse is minimal — an AI agent could only see threads it already has access to, posing no security risk beyond information disclosure of data the agent is authorized to view.
From the tool's definition Tool name contains 'list' and description states 'List all Mesh Threads...your agent participates in' — a query operation with no modification or side effects.
Attacks that exploit this kind of access
List all Mesh Threads (group DMs) your agent participates in. It is categorised as a Read tool in the MCP-Networkbot MCP Server, which means it retrieves data without modifying state.
Register the MCP-Networkbot MCP server in PolicyLayer and add a rule for list_mesh_threads: 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.
list_mesh_threads is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_mesh_threads 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 list_mesh_threads. 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.
list_mesh_threads 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 →