Removes a registered controller by name. If it is the currently connected controller, the connection is closed.
AI agents call remove_controller to permanently remove resources in nomos MCP Bridge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a registered controller is an irreversible action that destroys configuration state. While it does not delete user data directly, it permanently eliminates a system integration and will disrupt active connections. This qualifies as Destructive rather than Write because the deletion cannot be easily undone without re-registering the controller.
From the tool's definition 'Removes a registered controller by name' — this operation irreversibly deletes a controller registration and closes the connection if it is active.
Attacks that exploit this kind of access
Removes a registered controller by name. If it is the currently connected controller, the connection is closed. It is categorised as a Destructive tool in the nomos MCP Bridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the nomos MCP Bridge MCP server in PolicyLayer and add a rule for remove_controller: 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.
remove_controller is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_controller 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 remove_controller. 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.
remove_controller 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 →