# list_answers

List Answers (contract v0), paginated with an opaque cursor. Read-only.

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

## Facts

- Tool: `list_answers`
- 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: 2
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no | Max answers to return (default: loader's choice, capped 200). |
| `cursor` | string | no | Opaque pagination cursor from a previous list_answers call's nextCursor. |

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

## Why list_answers is rated Low

Even though list_answers 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.

## Use case

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

## 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_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_guides` — Read — https://policylayer.com/tools/com-aiengineerprofessional-guide-registry/list-guides.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