rhino_bridge_list_instances
Enumerate live Rhino bridge endpoints discovered via announcement files.
This record as markdown: /tools/easehee-rhino-mcp/rhino-bridge-list-instances.md
What rhino_bridge_list_instances does on Rhino
AI agents call rhino_bridge_list_instances to retrieve information from Rhino without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why rhino_bridge_list_instances is rated Low
The tool performs discovery/enumeration of existing bridge instances, which is a read-only operation with no side effects. It gathers metadata about what Rhino bridge endpoints are available. This has minimal security risk as it only retrieves status information.
From the tool's definition Tool name contains 'list' and description says 'Enumerate live Rhino bridge endpoints discovered via announcement files' — this is a query operation that retrieves information about available endpoints without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs rhino_bridge_list_instances safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rhino, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rhino_bridge_list_instances, this is the rule to start with:
rhino_bridge_list_instances is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rhino, apply this rule, and every rhino_bridge_list_instances call is checked against it from then on.
Questions about rhino_bridge_list_instances
Enumerate live Rhino bridge endpoints discovered via announcement files. It is categorised as a Read tool in the Rhino MCP Server, which means it retrieves data without modifying state.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_bridge_list_instances: 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 Rhino. Nothing to install.
rhino_bridge_list_instances 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 rhino_bridge_list_instances 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 rhino_bridge_list_instances. 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.
rhino_bridge_list_instances is provided by the Rhino MCP server (easehee/rhino-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rhino, and thousands of servers like it.
This server
Across the catalogue