# prts_page

A read tool on the Prts MCP server.

Agent View of the PolicyLayer registry record for `prts_page`. HTML page: https://policylayer.com/tools/3akhp-prts-mcp/prts-page

## Facts

- Tool: `prts_page`
- Server: Prts (`3akhp/prts-mcp`) — https://policylayer.com/tools/3akhp-prts-mcp.md
- Homepage: https://github.com/3aKHP/prts-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- 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": "prts_page",
    "arguments": {}
  }
}
```

## Why prts_page is rated Low

This tool almost certainly retrieves wiki page content from the PRTS (Arknights) database. The empty description is a minor confidence penalty, but the context of sibling Read-category tools and the server's stated purpose (querying and extracting data) strongly indicate it performs lookups only. No capability to modify, delete, execute, or incur financial impact is evident.

From the tool's own definition: "Tool name 'prts_page' on an Arknights wiki server with sibling tools like 'get_operator_archives', 'get_operator_voicelines', 'get_stage_enemies', and 'get_item_info' indicates a retrieval function."

## Use case

AI agents call prts_page to retrieve information from Prts 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 Prts:

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

## Other tools on Prts (10)

- `find_character_appearances` — Read — https://policylayer.com/tools/3akhp-prts-mcp/find-character-appearances.md
- `find_speakers_in` — Read — https://policylayer.com/tools/3akhp-prts-mcp/find-speakers-in.md
- `get_operator_memoirs` — Read — https://policylayer.com/tools/3akhp-prts-mcp/get-operator-memoirs.md
- `get_story_summary` — Read — https://policylayer.com/tools/3akhp-prts-mcp/get-story-summary.md
- `list_stories` — Read — https://policylayer.com/tools/3akhp-prts-mcp/list-stories.md
- `list_story_events` — Read — https://policylayer.com/tools/3akhp-prts-mcp/list-story-events.md
- `read_activity` — Read — https://policylayer.com/tools/3akhp-prts-mcp/read-activity.md
- `read_story` — Read — https://policylayer.com/tools/3akhp-prts-mcp/read-story.md
- `search_prts` — Read — https://policylayer.com/tools/3akhp-prts-mcp/search-prts.md
- `search_stories` — Read — https://policylayer.com/tools/3akhp-prts-mcp/search-stories.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=3akhp-prts-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/3akhp-prts-mcp