ebpf
eBPF/Falco: list eBPF programs, Falco status, deploy rules, read events
This record as markdown: /tools/defense/ebpf.md
What ebpf does on Defense
AI agents invoke ebpf to trigger actions in Defense. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
lines | number | — | Number of recent events to return |
action | string | Yes | eBPF/Falco security action |
dryRun | boolean | — | Preview only |
priority | string | — | Filter by minimum priority |
ruleName | string | — | Rule file name without .yaml extension |
ruleContent | string | — | YAML rule content |
Parameters from the server's own tool schema.
Why ebpf is rated High
eBPF (extended Berkeley Packet Filter) and Falco rule deployment constitute code execution on the kernel/system level. Deploying rules or eBPF programs can alter system behavior, trigger security monitoring, or modify how traffic is processed. While this is a defensive tool used for security hardening and threat detection, the capability to deploy and execute code at the system level makes it an Execute-class risk.
From the tool's definition The tool description explicitly states 'deploy rules' and 'read events', indicating it can execute eBPF programs and deploy Falco rules to a running system.
Attacks that exploit this kind of access
The rule that runs ebpf safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Defense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ebpf, this is the rule to start with:
ebpf 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Defense, apply this rule, and every ebpf call is checked against it from then on.
Questions about ebpf
eBPF/Falco: list eBPF programs, Falco status, deploy rules, read events. It is categorised as a Execute tool in the Defense MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
ebpf accepts 6 parameters: lines, action, dryRun, priority, ruleName, ruleContent. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Defense MCP server in PolicyLayer and add a rule for ebpf: 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 Defense. Nothing to install.
ebpf 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 ebpf 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 ebpf. 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.
ebpf is provided by the Defense MCP server (defense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Defense, and thousands of servers like it.
Across the catalogue