# get_resource

Get one guide, question page, or blog post by slug — its title, description, and content (blog body markdown, or the FAQ question/answer pairs for guides and question pages).

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

## Facts

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

## Why get_resource is rated Low

This is a straightforward data retrieval operation that fetches and returns the content of existing resources without creating, modifying, deleting, or executing any operations. No side effects or state changes occur. The low severity reflects minimal risk even if misused—an agent could retrieve content repeatedly but cannot alter or delete it.

From the tool's own definition: "Tool retrieves specific resources (guides, question pages, blog posts) by slug and returns title, description, and content. Server explicitly described as 'Read-only.' Tool name and description indicate data retrieval with no modification capabilities."

## Use case

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

## 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
- `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