create_context

What create_context does on Ncp

AI agents invoke create_context to trigger actions in Ncp. 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.

Why create_context is rated High

Creating a browser context is an Execute-category action because it triggers an external operation (instantiating a browser environment). While the creation itself is not inherently destructive or financial, a browser context enables a wide range of subsequent actions (navigation, script execution, data access), giving it medium severity due to the blast radius if misused by an AI agent.

From the tool's definition 'Create a new browser context' — spawns a browser context, which is an external operation that initializes a browser environment capable of subsequent browsing, scripting, and network actions

The rule that runs create_context safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_context, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_context": {
      "limits": [
        {
          "counter": "create_context_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about create_context