Get revision history for an episode.
AI agents call get_episode_revisions to retrieve information from Bangumi TV MCP Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves revision history information about an episode. It performs a read-only operation that retrieves existing data from the BangumiTV API with no capability to modify, delete, or execute actions. The action is purely informational retrieval, consistent with other Read category tools on the same server (browse_subjects, get_character_details, get_character_image, etc.).
From the tool's definition Tool name 'get_episode_revisions' and description 'Get revision history for an episode' indicate retrieval of historical data without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_episode_revisions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bangumi TV MCP Service, and nothing reaches the server without passing your rules. This is the rule we recommend for get_episode_revisions:
{
"version": "1",
"default": "deny",
"tools": {
"get_episode_revisions": {}
}
} get_episode_revisions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get revision history for an episode. It is categorised as a Read tool in the Bangumi TV MCP Service MCP Server, which means it retrieves data without modifying state.
Register the Bangumi TV MCP Service MCP server in PolicyLayer and add a rule for get_episode_revisions: 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 Bangumi TV MCP Service. Nothing to install.
get_episode_revisions 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_episode_revisions 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_episode_revisions. 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_episode_revisions is provided by the Bangumi TV MCP Service MCP server (ukenn2112/bangumimcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bangumi TV MCP Service, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
46 Bangumi TV MCP Service tools catalogued and risk-classified — across an index of 43,000+ MCP servers.