This record as markdown: /tools/3akhp-prts-mcp/list-story-events.md
What list_story_events does on Prts
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.
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 definition Tool name 'list_story_events' and description '列出明日方舟剧情活动列表' ("list Arknights story event list") indicates a simple retrieval/listing operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_story_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Prts, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_story_events, this is the rule to start with:
list_story_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Prts, apply this rule, and every list_story_events call is checked against it from then on.
Questions about list_story_events
列出明日方舟剧情活动列表。. It is categorised as a Read tool in the Prts MCP Server, which means it retrieves data without modifying state.
Register the Prts MCP server in PolicyLayer and add a rule for list_story_events: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Prts. Nothing to install.
list_story_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_story_events rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_story_events. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_story_events is provided by the Prts MCP server (3akhp/prts-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Prts, and thousands of servers like it.
This server
Across the catalogue