# list_guides

List the bicycle.guide registry — every guide's home, status, access, standard, syndication and grounding, plus the distribution roll-up (including guides homed to a property with no rendering surface).

Agent View of the PolicyLayer registry record for `list_guides`. HTML page: https://policylayer.com/tools/com-aiengineerprofessional-guide-registry/list-guides

## Facts

- Tool: `list_guides`
- Server: Guide Registry (`https://aiengineerprofessional.com/mcp`) — https://policylayer.com/tools/com-aiengineerprofessional-guide-registry.md
- Homepage: https://github.com/people-analyst/bicycle-guide
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 12
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `home` | string | no | Filter by owning property, e.g. jobframe, peopleanalyst, penwright. |
| `limit` | number | no | Cap the rows returned. Default 100, max 500. |
| `access` | string | no | Filter by access: free \| gated. |
| `domain` | string | no | Filter by life-domain — the layer ABOVE the subject shelf: work \| life \| play. Derived from the guide's category via content/registry/shelves.json. `rollup.by_d |
| `fields` | string | no | Row shape. "compact" returns only slug/title/home/status/access/price_cents/has_artifact/category/domain/personas/canonical_url — no rollup, no registry_meta. " |
| `series` | string | no | Filter by guide series — the operational grouping of guides made to be used together, e.g. competencies, penwright-writing, startup-journey, ladder:hr-business- |
| `status` | string | no | Filter by status: on \| draft. |
| `persona` | string | no | Filter by the audience a guide serves, e.g. people-analytics-professional, aspiring-author, executive-performance-leader. A guide can serve several; this matche |
| `category` | string | no | Filter by subject shelf — the reader-facing topic axis, e.g. field, skills, analytics, writing, comp. Matches the primary category OR a cross-shelf tag. |
| `standard` | string | no | Filter by standard: bicycle \| life-stage \| problem-opportunity. |
| `guide_type` | string | no | Filter by guide CLASS: career (level-based job guides, their own program) \| capability \| book_profile. Combine with series=ladder:<role> to get one role's whole |
| `has_artifact` | boolean | no | Only guides that do (true) / do not (false) have a new-design artifact. |

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

## Why list_guides is rated Low

Even though list_guides only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: High parameter count (13 properties) · Bulk/mass operation — affects multiple targets

## Use case

AI agents call list_guides to retrieve information from Guide Registry 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 Guide Registry:

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

## Other tools on Guide Registry (9)

- `get_answer` — Read — https://policylayer.com/tools/com-aiengineerprofessional-guide-registry/get-answer.md
- `get_guide` — Read — https://policylayer.com/tools/com-aiengineerprofessional-guide-registry/get-guide.md
- `list_answers` — Read — https://policylayer.com/tools/com-aiengineerprofessional-guide-registry/list-answers.md
- `list_capabilities` — Read — https://policylayer.com/tools/com-aiengineerprofessional-guide-registry/list-capabilities.md
- `list_conditions` — Read — https://policylayer.com/tools/com-aiengineerprofessional-guide-registry/list-conditions.md
- `list_disagreements` — Read — https://policylayer.com/tools/com-aiengineerprofessional-guide-registry/list-disagreements.md
- `list_taxonomy` — Read — https://policylayer.com/tools/com-aiengineerprofessional-guide-registry/list-taxonomy.md
- `search_answers` — Read — https://policylayer.com/tools/com-aiengineerprofessional-guide-registry/search-answers.md
- `search_guides` — Read — https://policylayer.com/tools/com-aiengineerprofessional-guide-registry/search-guides.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-aiengineerprofessional-guide-registry · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-aiengineerprofessional-guide-registry