AI agents invoke comet_connect to trigger actions in Comet. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool initiates a connection to an external browser instance and can auto-start it if not running. It triggers an external operation (launching/connecting to a browser process), which places it in the Execute category. Misuse could result in unauthorized browser sessions or resource consumption, warranting medium severity.
From the tool's definition Connect to Comet browser (auto-starts if needed)
Attacks that exploit this kind of access
Connect to Comet browser (auto-starts if needed). It is categorised as a Execute tool in the Comet MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Comet MCP server in PolicyLayer and add a rule for comet_connect: 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 Comet. Nothing to install.
comet_connect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the comet_connect 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 comet_connect. 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.
comet_connect is provided by the Comet MCP server (simplicianokelly52/comet_mcp). 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 →