This record as markdown: /tools/3akhp-prts-mcp/prts-page.md
What prts_page does on Prts
AI agents call prts_page 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 prts_page is rated Low
This tool almost certainly retrieves wiki page content from the PRTS (Arknights) database. The empty description is a minor confidence penalty, but the context of sibling Read-category tools and the server's stated purpose (querying and extracting data) strongly indicate it performs lookups only. No capability to modify, delete, execute, or incur financial impact is evident.
From the tool's definition Tool name 'prts_page' on an Arknights wiki server with sibling tools like 'get_operator_archives', 'get_operator_voicelines', 'get_stage_enemies', and 'get_item_info' indicates a retrieval function.
Attacks that exploit this kind of access
The rule that runs prts_page 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 prts_page, this is the rule to start with:
prts_page 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 prts_page call is checked against it from then on.
Questions about prts_page
prts_page 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.
Register the Prts MCP server in PolicyLayer and add a rule for prts_page: 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.
prts_page 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 prts_page 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 prts_page. 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.
prts_page 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