This record as markdown: /tools/mcp-control-plane/bridge-ports.md
What bridge_ports does on Mcp Control Plane
AI agents call bridge_ports to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why bridge_ports is rated Low
This tool retrieves or queries bridge port information with no side effects. It does not create, modify, delete, or execute operations—it simply returns data. This is a classic Read operation with minimal security risk unless the returned data itself is sensitive, but the action performed is purely informational.
From the tool's definition Tool name 'bridge_ports' and description 'Return bridge ports' indicate a query/retrieval operation that returns information about network bridge ports without modifying or executing actions.
Attacks that exploit this kind of access
The rule that runs bridge_ports safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bridge_ports, this is the rule to start with:
bridge_ports 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 Mcp Control Plane, apply this rule, and every bridge_ports call is checked against it from then on.
Questions about bridge_ports
Return bridge ports. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for bridge_ports: 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 Control Plane. Nothing to install.
bridge_ports 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 bridge_ports 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 bridge_ports. 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.
bridge_ports is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue