browse_members
AI agents call browse_members 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.
The tool name strongly indicates data retrieval (browse/list members) without modification or execution capability. The absence of a description lowers confidence slightly, but the naming convention and sibling tools support classification as Read. No evidence of deletion, code execution, financial operations, or irreversible modifications.
From the tool's definition Tool name 'browse_members' suggests querying or listing members of a network; no description provided. Sibling tools like 'get_matches', 'get_anchor_posts', and 'get_agent_pulse' are read-only queries, suggesting this tool follows similar read-access patterns.
Attacks that exploit this kind of access
browse_members. 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 browse_members: 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.
browse_members 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 browse_members 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 browse_members. 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.
browse_members 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 →