AI agents call get_weekly_anime_releases to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns information about anime release dates—a read-only operation that retrieves data without side effects. The 6-day window (3 past, 3 future) is a fixed parameter, not user-controlled execution. No data is modified, deleted, or financial transactions occur. Low severity reflects minimal risk even if misused.
From the tool's definition Tool description states 'Gibt eine Liste zurück' (returns a list) of anime releases. This is a retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Gibt eine Liste zurück mit Anime-Erscheinungen der letzten 3 vergangenen Tage und 3 kommenden Tage. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for get_weekly_anime_releases: 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 Mcp. Nothing to install.
get_weekly_anime_releases 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_weekly_anime_releases 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_weekly_anime_releases. 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_weekly_anime_releases is provided by the MCP server (laurensanp/mcp-server). 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 →