# get_introduction_path

Get the public directory URL and what an introduction to a firm requires. READ-ONLY: returns instructions only — it does not submit a request or create a lead.

Agent View of the PolicyLayer registry record for `get_introduction_path`. HTML page: https://policylayer.com/tools/com-grcmigrate-directory/get-introduction-path

## Facts

- Tool: `get_introduction_path`
- 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: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `firm_slug` | string | yes |  |

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": "get_introduction_path",
    "arguments": {
      "firm_slug": "<firm_slug>"
    }
  }
}
```

## Why get_introduction_path is rated Low

This tool retrieves and returns information (public directory URL and introduction requirements) with no side effects. No data is created, modified, deleted, or executed. The explicit 'READ-ONLY' designation and the fact that it 'returns instructions only' without submitting requests or creating leads confirms this is a simple read/retrieval operation with minimal blast radius.

From the tool's own definition: "Tool description explicitly states 'READ-ONLY: returns instructions only — it does not submit a request or create a lead.' The tool retrieves public directory information and guidance without creating, modifying, or executing any actions."

## Use case

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

## Other tools on Directory (4)

- `get_firm` — Read — https://policylayer.com/tools/com-grcmigrate-directory/get-firm.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
- `search_firms` — Read — https://policylayer.com/tools/com-grcmigrate-directory/search-firms.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