# list_emba_scans

A read tool on the EMBA-MCP MCP server.

Agent View of the PolicyLayer registry record for `list_emba_scans`. HTML page: https://policylayer.com/tools/0xbuz3r-emba-mcp/list-emba-scans

## Facts

- Tool: `list_emba_scans`
- 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": "list_emba_scans",
    "arguments": {}
  }
}
```

## Why list_emba_scans is rated Low

The 'list_' prefix conventionally denotes read-only retrieval. No description is provided, but the pattern matches sibling tools like 'get_emba_scan_status' which query existing data. Listed firmware scans are informational artifacts; accessing them has no side effects on the firmware, system, or security posture. Confidence is slightly reduced due to missing description, but the naming convention is clear.

From the tool's own definition: "Tool name 'list_emba_scans' indicates a listing/querying operation. Description is empty, but the tool name and context (sibling tools query firmware analysis results) strongly suggest this retrieves a list of previously run EMBA scans without modification or…"

## Use case

AI agents call list_emba_scans 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": {
    "list_emba_scans": {}
  }
}
```

## 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_kernel_info` — Read — https://policylayer.com/tools/0xbuz3r-emba-mcp/get-kernel-info.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
- `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