start_devtools_monitoring

What start_devtools_monitoring does on Percepta MCP Server

AI agents invoke start_devtools_monitoring to trigger actions in Percepta MCP Server. 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 start_devtools_monitoring is rated High

This tool executes an operation (monitoring activation) on an external system (browser DevTools) whose effects persist and depend on how the monitoring is configured and what data flows through it. While not inherently destructive or financially risky, it triggers external behavior beyond simple data retrieval and is more invasive than a Read operation.

From the tool's definition Tool name 'start_devtools_monitoring' and description 'Start monitoring DevTools data for a web page' indicates activation of browser DevTools monitoring—an external operation with effects that depend on runtime arguments (which page, what data to capture).

The rule that runs start_devtools_monitoring safely

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

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

Questions about start_devtools_monitoring