# execute_bpftrace_background

Start a BPFtrace script in the background and return immediately with a job_id. Use get_job_output to poll for output, kill_job to stop it.

Agent View of the PolicyLayer registry record for `execute_bpftrace_background`. HTML page: https://policylayer.com/tools/42research-dynamic-mcp/execute-bpftrace-background

## Facts

- Tool: `execute_bpftrace_background`
- Server: Dynamic MCP Server (`42research/dynamic_mcp`) — https://policylayer.com/tools/42research-dynamic-mcp.md
- Homepage: https://github.com/42Research/dynamic_mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "execute_bpftrace_background",
    "arguments": {}
  }
}
```

## Why execute_bpftrace_background is rated High

This tool executes arbitrary BPFtrace scripts at kernel level, which can inspect and modify kernel state, access sensitive memory, and trigger system-level side effects. The effects depend on the script content provided by the agent. While not immediately destructive or financial, unauthorized execution could crash systems, leak sensitive data, or enable privilege escalation.

From the tool's own definition: "Tool description states it 'Start[s] a BPFtrace script in the background' and returns a job_id for polling. BPFtrace is a dynamic tracing tool that executes kernel-level code."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Dynamic MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_bpftrace_background": {
      "limits": [
        {
          "counter": "execute_bpftrace_background_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Dynamic MCP Server (15)

- `crash_command` — Execute — https://policylayer.com/tools/42research-dynamic-mcp/crash-command.md
- `execute_bash_background` — Execute — https://policylayer.com/tools/42research-dynamic-mcp/execute-bash-background.md
- `execute_bash_command` — Execute — https://policylayer.com/tools/42research-dynamic-mcp/execute-bash-command.md
- `execute_bpftrace_script` — Execute — https://policylayer.com/tools/42research-dynamic-mcp/execute-bpftrace-script.md
- `start_crash_session` — Execute — https://policylayer.com/tools/42research-dynamic-mcp/start-crash-session.md
- `get_bpftrace_info` — Read — https://policylayer.com/tools/42research-dynamic-mcp/get-bpftrace-info.md
- `get_crash_info` — Read — https://policylayer.com/tools/42research-dynamic-mcp/get-crash-info.md
- `get_job_output` — Read — https://policylayer.com/tools/42research-dynamic-mcp/get-job-output.md
- `get_source_file` — Read — https://policylayer.com/tools/42research-dynamic-mcp/get-source-file.md
- `kill_job` — Read — https://policylayer.com/tools/42research-dynamic-mcp/kill-job.md
- `list_crash_dumps` — Read — https://policylayer.com/tools/42research-dynamic-mcp/list-crash-dumps.md
- `list_jobs` — Read — https://policylayer.com/tools/42research-dynamic-mcp/list-jobs.md
- `list_source_files` — Read — https://policylayer.com/tools/42research-dynamic-mcp/list-source-files.md
- `search_source_files` — Read — https://policylayer.com/tools/42research-dynamic-mcp/search-source-files.md
- `close_crash_session` — Write — https://policylayer.com/tools/42research-dynamic-mcp/close-crash-session.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=42research-dynamic-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/42research-dynamic-mcp
