read_story

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/read-story.md

WHAT IT DOES

What read_story does on Prts

AI agents call read_story 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 read_story is rated Low

This tool retrieves story content from the Arknights PRTS Wiki—a read-only query operation with no side effects, data modification, execution of external code, or financial impact. The server is explicitly designed for 'fan-creation AI agents' to access lore and narrative content. No destructive, write, execute, or financial capabilities are present.

From the tool's definition Tool name 'read_story' combined with server purpose of querying/serving game lore, character profiles, story scripts, and event scripts.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

read_story Allowed

read_story 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": {
    "read_story": {}
  }
}

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 read_story call is checked against it from then on.

FAQ

Questions about read_story

What does the read_story tool do? +

read_story 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 read_story? +

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

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

Can I rate-limit read_story? +

Yes. Add a rate_limit block to the read_story 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 read_story completely? +

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

read_story 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

binary_read on 010 Editor → The MCP Attack Database →

Guides

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