container_isolation
Container isolation: AppArmor, SELinux, namespaces, seccomp, rootless setup
This record as markdown: /tools/defense/container-isolation.md
What container_isolation does on Defense
AI agents invoke container_isolation 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 |
|---|---|---|---|
pid | number | — | Process ID to inspect |
mode | string | — | SELinux mode |
action | string | Yes | Action to perform |
dryRun | boolean | — | Preview only |
dry_run | boolean | — | Preview changes without executing |
profile | string | — | AppArmor profile name |
username | string | — | Username to configure |
allowWrite | array | — | Writable paths |
check_type | string | — | Namespace check type |
outputPath | string | — | Output path for profile |
profileName | string | — | Profile name for container/seccomp |
subuidCount | number | — | Subordinate UID count |
Parameters from the server's own tool schema.
Why container_isolation is rated High
This tool configures and applies mandatory access control (AppArmor/SELinux profiles), kernel namespace isolation, seccomp filters, and rootless container setup. These are active system-level security enforcement mechanisms that modify kernel security policies and container runtime configurations.
From the tool's definition Container isolation: AppArmor, SELinux, namespaces, seccomp, rootless setup
Risk signalsHigh parameter count (18 properties)
Attacks that exploit this kind of access
The rule that runs container_isolation 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 container_isolation, this is the rule to start with:
container_isolation 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 container_isolation call is checked against it from then on.
Questions about container_isolation
Container isolation: AppArmor, SELinux, namespaces, seccomp, rootless setup. 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.
container_isolation accepts 12 parameters: pid, mode, action, dryRun, dry_run, profile, username, allowWrite, check_type, outputPath, profileName, subuidCount. 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 container_isolation: 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.
container_isolation 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 container_isolation 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 container_isolation. 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.
container_isolation 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