AI agents call get_chapter_access_info to retrieve information from Mangadex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries chapter metadata (access URLs and reader links) from the MangaDex API with no side effects, data modification, or irreversible actions. It is a straightforward data retrieval operation that poses minimal security risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Return[s] chapter access metadata only' and explicitly notes it does not provide download URLs. The tool name includes 'get_' prefix and the description uses 'Return', indicating retrieval without modification or side effects.
Attacks that exploit this kind of access
Return chapter access metadata only, including the MangaDex reader URL or external host URL. MangaDex does not provide PDF/CBZ download URLs here. It is categorised as a Read tool in the Mangadex MCP Server, which means it retrieves data without modifying state.
Register the Mangadex MCP server in PolicyLayer and add a rule for get_chapter_access_info: 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 Mangadex. Nothing to install.
get_chapter_access_info 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 get_chapter_access_info 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 get_chapter_access_info. 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.
get_chapter_access_info is provided by the Mangadex MCP server (kenhendricks00/mangadex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →