Get details of a specific person revision.
AI agents call get_person_revision 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 retrieves and queries revision details for a person entity. The verb 'Get' and absence of any modification, deletion, or execution capability clearly indicate a Read operation. It retrieves historical version information without side effects. The low severity reflects that accessing revision metadata poses minimal risk—no data is modified, deleted, or executed.
From the tool's definition Tool name 'get_person_revision' and description 'Get details of a specific person revision' indicate retrieval of revision history data with no modification capability.
Documented attack patterns abuse exactly the kind of access get_person_revision 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_person_revision:
{
"version": "1",
"default": "deny",
"tools": {
"get_person_revision": {}
}
} get_person_revision 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 details of a specific person revision. 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_person_revision: 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_person_revision 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_person_revision 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_person_revision. 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_person_revision 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.