Lists all registered nomos controllers with their names, URLs, and which one is currently active.
AI agents call list_controllers 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 performs a read-only operation that retrieves configuration information about registered controllers. It has no capability to modify, delete, or execute actions on the smart home system. The blast radius is minimal—an AI agent calling this tool can only learn what controllers are registered and which is active, posing no direct risk to system integrity or operations.
From the tool's definition Tool name 'list_controllers' and description 'Lists all registered nomos controllers with their names, URLs, and which one is currently active' indicate a query operation that retrieves information without modification or side effects.
Attacks that exploit this kind of access
Lists all registered nomos controllers with their names, URLs, and which one is currently 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 list_controllers: 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.
list_controllers 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 list_controllers 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 list_controllers. 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.
list_controllers 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 →