# list_story_events

列出明日方舟剧情活动列表。

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

## Facts

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

## Why list_story_events is rated Low

This tool queries and returns a list of story events from the Arknights game. It performs a read-only retrieval operation analogous to list or fetch operations. There is no data modification, code execution, deletion, or financial impact. Even if an AI agent misuses this tool, it can only retrieve already-public game event data, posing minimal risk.

From the tool's own definition: "Tool name 'list_story_events' and description '列出明日方舟剧情活动列表' ('list Arknights story event list') indicates a simple retrieval/listing operation with no side effects."

## Use case

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

## 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
- `prts_page` — Read — https://policylayer.com/tools/3akhp-prts-mcp/prts-page.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