Get the detailed seichi junrei (anime pilgrimage) locations for a specific anime using its Bangumi ID.
AI agents call get_anime_detail_points to retrieve information from Anitabi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries an API to fetch geographic and metadata information about anime pilgrimage locations. It has no side effects, does not modify data, execute code, delete information, or involve financial transactions. It is purely informational retrieval, fitting the Read category.
From the tool's definition Tool retrieves 'detailed seichi junrei (anime pilgrimage) locations' and 'geographic coordinates' for a specified anime.
Attacks that exploit this kind of access
Get the detailed seichi junrei (anime pilgrimage) locations for a specific anime using its Bangumi ID. It is categorised as a Read tool in the Anitabi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Anitabi MCP Server MCP server in PolicyLayer and add a rule for get_anime_detail_points: 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 Anitabi MCP Server. Nothing to install.
get_anime_detail_points 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_anime_detail_points 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_anime_detail_points. 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_anime_detail_points is provided by the Anitabi MCP Server MCP server (thinktraveller/anitabi_mcpserver). 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 →