get_person_revisions

THE RISK

Low Risk

Why get_person_revisions needs a policy

This tool only retrieves past revision records for a person entity. It queries existing data without side effects, fitting the Read category. The severity is low because revision history is typically non-sensitive metadata that poses minimal risk if retrieved inappropriately.

From the tool's definition Tool name 'get_person_revisions' and description 'Get revision history for a person' indicate retrieval of historical data with no modification or deletion capabilities.

Documented attack patterns abuse exactly the kind of access get_person_revisions gives an agent:

POLICY

How to control get_person_revisions

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_revisions:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_person_revisions": {}
  }
}

get_person_revisions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Bangumi TV MCP Service — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bangumi TV MCP Service tools

Destructive uncollect_character Remove a character from the current user's collection. Destructive uncollect_person Remove a person from the current user's collection. Write collect_character Collect (favorite) a character for the current user. Write collect_person Collect (favorite) a person for the current user. Write update_episode_collection update_episode_collection Write update_single_episode_collection Update the collection status for a single episode. Write update_subject_collection update_subject_collection Read browse_subjects browse_subjects

All 46 Bangumi TV MCP Service tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_person_revisions

What does the get_person_revisions tool do? +

Get revision history for a person. It is categorised as a Read tool in the Bangumi TV MCP Service MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_person_revisions? +

Register the Bangumi TV MCP Service MCP server in PolicyLayer and add a rule for get_person_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.

What risk level is get_person_revisions? +

get_person_revisions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_person_revisions? +

Yes. Add a rate_limit block to the get_person_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.

How do I block get_person_revisions completely? +

Set action: deny in the PolicyLayer policy for get_person_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.

What MCP server provides get_person_revisions? +

get_person_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.

Enforce policy on every Bangumi TV MCP Service tool call.

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.

CHECK YOUR STACK →