list_stories

A read tool on the Prts MCP server.

SERVERPrts SOURCE3akhp/prts-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/3akhp-prts-mcp/list-stories.md

WHAT IT DOES

What list_stories does on Prts

AI agents call list_stories 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.

RISK

Why list_stories is rated Low

The tool lists story data from an Arknights wiki/game database. No description provided, but the naming pattern and server purpose strongly suggest read-only retrieval of story metadata or indices. This aligns with the server's stated function of serving 'lore, character profiles, and in-character dialogue' to fan-creation agents. No side effects or data modification implied.

From the tool's definition Tool name 'list_stories' and server context indicate data retrieval; description is empty but sibling tools (get_operator_archives, get_operator_voicelines, get_prts_categories) are all read-only query functions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_stories 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_stories, this is the rule to start with:

list_stories Allowed

list_stories is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_stories": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Prts, apply this rule, and every list_stories call is checked against it from then on.

FAQ

Questions about list_stories

What does the list_stories tool do? +

list_stories is a read tool on the Prts MCP server. It is categorised as a Read tool in the Prts MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_stories? +

Register the Prts MCP server in PolicyLayer and add a rule for list_stories: 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.

What risk level is list_stories? +

list_stories is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_stories? +

Yes. Add a rate_limit block to the list_stories 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.

How do I block list_stories completely? +

Set action: deny in the PolicyLayer policy for list_stories. 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.

What MCP server provides list_stories? +

list_stories 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.

KEEP EXPLORING

More on Prts, and thousands of servers like it.

This server

All 11 Prts tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →