# list_resources

List GRC Migrate guides, question pages, and blog posts available to read (title, description, url, type). Read-only.

Agent View of the PolicyLayer registry record for `list_resources`. HTML page: https://policylayer.com/tools/com-grcmigrate-directory/list-resources

## Facts

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

## Why list_resources is rated Low

This tool retrieves and lists informational resources without side effects. It is a straightforward read operation that queries available compliance and migration documentation. The explicit 'Read-only' designation and lack of any write, execute, or destructive operations confirm low severity and high confidence classification in the Read category.

From the tool's own definition: "Tool description explicitly states 'Read-only' and lists operations are retrieval-focused: 'List GRC Migrate guides, question pages, and blog posts' with metadata (title, description, url, type). No modification, deletion, or execution capability described."

## Use case

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

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