get_story_summary

获取单章剧情的梗概。

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

WHAT IT DOES

What get_story_summary does on Prts

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

This tool queries and retrieves story summaries from the PRTS Wiki—a read-only data retrieval operation with no side effects. The blast radius of misuse is minimal; an AI agent could only retrieve unwanted narrative content, which poses no operational risk.

From the tool's definition Tool name 'get_story_summary' and description '获取单章剧情的梗概' (get story summary for a single chapter) indicate retrieval of narrative/lore content. No modification, deletion, code execution, or financial operations are involved.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_story_summary Allowed

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

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

FAQ

Questions about get_story_summary

What does the get_story_summary tool do? +

获取单章剧情的梗概。. 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 get_story_summary? +

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

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

Can I rate-limit get_story_summary? +

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

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

get_story_summary 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

get_summary on ACE-MCP →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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