List all Agent Rooms — curated + community rooms with their slugs.
AI agents call get_rooms 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 is a straightforward query/list operation that retrieves and presents existing data about rooms without creating, modifying, deleting, or executing any actions. The read-only nature and passive information retrieval make this low severity with high confidence.
From the tool's definition Tool name is 'get_rooms' and description states 'List all Agent Rooms' — a retrieval operation with no side effects. Returns room metadata (slugs and names) only.
Attacks that exploit this kind of access
List all Agent Rooms — curated + community rooms with their slugs. 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 get_rooms: 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.
get_rooms 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 get_rooms 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 get_rooms. 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.
get_rooms 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 →