start_electron_main_cpu_profile

WHAT IT DOES

What start_electron_main_cpu_profile does on Electron

AI agents invoke start_electron_main_cpu_profile to trigger actions in Electron. 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 IT NEEDS A POLICY

Why start_electron_main_cpu_profile needs a policy

CPU profiling is an instrumentation action that modifies the runtime behavior of the target process. While not destructive or financial, it triggers external operations (profiling) whose effects depend on the profiling parameters and target process state.

From the tool's definition start_electron_main_cpu_profile initiates CPU profiling via Chrome DevTools Protocol (CDP) on an Electron main process. The tool directly instructs the Electron process to begin capturing CPU usage data, which is a form of process instrumentation/control.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_electron_main_cpu_profile Rate-limited

start_electron_main_cpu_profile stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Electron, so you can run agents against it safely.

FAQ

Questions about start_electron_main_cpu_profile

What does the start_electron_main_cpu_profile tool do? +

Start CPU profiling in main process. Call stop to get results. It is categorised as a Execute tool in the Electron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_electron_main_cpu_profile? +

Register the Electron MCP server in PolicyLayer and add a rule for start_electron_main_cpu_profile: 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 Electron. Nothing to install.

What risk level is start_electron_main_cpu_profile? +

start_electron_main_cpu_profile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_electron_main_cpu_profile? +

Yes. Add a rate_limit block to the start_electron_main_cpu_profile 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.

How do I block start_electron_main_cpu_profile completely? +

Set action: deny in the PolicyLayer policy for start_electron_main_cpu_profile. 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.

What MCP server provides start_electron_main_cpu_profile? +

start_electron_main_cpu_profile is provided by the Electron MCP server (ohah/electron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.