# get_kernel_info

A read tool on the EMBA-MCP MCP server.

Agent View of the PolicyLayer registry record for `get_kernel_info`. HTML page: https://policylayer.com/tools/0xbuz3r-emba-mcp/get-kernel-info

## Facts

- Tool: `get_kernel_info`
- Server: EMBA-MCP (`0xbuz3r/emba-mcp`) — https://policylayer.com/tools/0xbuz3r-emba-mcp.md
- Homepage: https://github.com/0xbuz3R/EMBA-MCP
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why get_kernel_info is rated Low

This tool retrieves kernel information from EMBA firmware analysis results. The 'get_' prefix indicates a read-only query operation. While the description is empty, the naming convention and context of sibling tools on the same EMBA analysis server—which query security findings, protection mechanisms, and system details—strongly suggests this retrieves kernel details for analysis purposes without side effects or…

From the tool's own definition: "Tool name 'get_kernel_info' with 'get_' prefix and 'info' suffix, following the pattern of sibling tools like 'get_binary_protection_mechanisms', 'get_bootloader_info', 'get_credentials_and_secrets', and 'get_filesystem_overview' which all retrieve firmware…"

## Use case

AI agents call get_kernel_info to retrieve information from EMBA-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches EMBA-MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_kernel_info": {}
  }
}
```

## Other tools on EMBA-MCP (19)

- `run_emba_scan` — Execute — https://policylayer.com/tools/0xbuz3r-emba-mcp/run-emba-scan.md
- `stop_emba_scan` — Execute — https://policylayer.com/tools/0xbuz3r-emba-mcp/stop-emba-scan.md
- `explain_attack_path` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/explain-attack-path.md
- `get_binary_protection_mechanisms` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-binary-protection-mechanisms.md
- `get_bootloader_info` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-bootloader-info.md
- `get_credentials_and_secrets` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-credentials-and-secrets.md
- `get_distribution_info` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-distribution-info.md
- `get_emba_scan_status` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-emba-scan-status.md
- `get_filesystem_overview` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-filesystem-overview.md
- `get_high_risk_findings` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-high-risk-findings.md
- `get_interesting_files` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-interesting-files.md
- `get_network_services` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-network-services.md
- `get_permissions_issues` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-permissions-issues.md
- `get_php_vulnerabilities` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-php-vulnerabilities.md
- `get_sbom` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-sbom.md
- `get_weak_crypto_and_keys` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-weak-crypto-and-keys.md
- `get_weak_functions` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-weak-functions.md
- `list_emba_scans` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/list-emba-scans.md
- `search_password_files` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/search-password-files.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=0xbuz3r-emba-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xbuz3r-emba-mcp