# search_firms

Search the GRC Migrate directory of SOC 2 audit and compliance-readiness firms (facts compiled from public sources). Filter by framework, ecosystem, partner status, or category. Read-only.

Agent View of the PolicyLayer registry record for `search_firms`. HTML page: https://policylayer.com/tools/com-grcmigrate-directory/search-firms

## Facts

- Tool: `search_firms`
- Server: Directory (`https://grcmigrate.com/mcp`) — https://policylayer.com/tools/com-grcmigrate-directory.md
- Homepage: https://github.com/https://grcmigrate.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 4
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `category` | string | no | e.g. "pen_test", "vciso_advisory" |
| `ecosystem` | string | no | compliance platform ecosystem, e.g. "vanta" or "drata" |
| `framework` | string | no | e.g. "SOC 2", "ISO 27001", "HIPAA" |
| `partner_status` | string | no | only "listed" or "partner"; "suppressed" is never valid |

Parameters from the server's own tool schema.

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

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

## Why search_firms is rated Low

This tool performs a search and filter operation on a directory of compliance firms—a pure information retrieval function with no side effects. The explicit 'read-only' designation confirms it cannot modify data or trigger external actions. The blast radius of misuse is minimal; an agent could only retrieve publicly-compiled directory information.

From the tool's own definition: "Tool description explicitly states 'Search the GRC Migrate directory' and 'Read-only.' The search operation retrieves firm data from a directory without modifying, deleting, or executing external operations."

## Use case

AI agents call search_firms to retrieve information from Directory 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 Directory:

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

## Other tools on Directory (4)

- `get_firm` — Read — https://policylayer.com/tools/com-grcmigrate-directory/get-firm.md
- `get_introduction_path` — Read — https://policylayer.com/tools/com-grcmigrate-directory/get-introduction-path.md
- `get_resource` — Read — https://policylayer.com/tools/com-grcmigrate-directory/get-resource.md
- `list_resources` — Read — https://policylayer.com/tools/com-grcmigrate-directory/list-resources.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=com-grcmigrate-directory · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-grcmigrate-directory