Shows the current connection status — which controller is connected and whether the connection is active.
AI agents call connection_status to retrieve information from nomos MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current state of the connection (which controller is active, whether it is connected) with no side effects. It is purely informational retrieval, fitting the Read category. The low severity reflects that exposing connection status information poses minimal risk—it cannot trigger actions, modify state, or cause harm.
From the tool's definition Tool name 'connection_status' and description 'Shows the current connection status' indicate a read-only operation that retrieves state information without modifying or executing anything.
Attacks that exploit this kind of access
Shows the current connection status — which controller is connected and whether the connection is active. It is categorised as a Read tool in the nomos MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the nomos MCP Bridge MCP server in PolicyLayer and add a rule for connection_status: 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 nomos MCP Bridge. Nothing to install.
connection_status 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 connection_status 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 connection_status. 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.
connection_status is provided by the nomos MCP Bridge MCP server (nomos-system/nomos-mcp-bridge). 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 →