Low Risk

get_current_user

Get the current user's information.

How to control get_current_user ↓

What get_current_user does on Bangumi TV MCP Service

AI agents call get_current_user 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.

Low Risk

Why get_current_user needs a policy

This is a straightforward read operation that retrieves existing user information. It performs no data modification, deletion, code execution, or financial transactions. The blast radius is minimal—the worst outcome is exposure of the user's own profile data, which is typically low sensitivity in a media/anime database context. Confidence is high due to clear intent from both the name and description.

From the tool's definition Tool name 'get_current_user' and description 'Get the current user's information' indicate retrieval of user profile data with no modification or side effects.

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

How to control get_current_user

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_current_user": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_current_user

What does the get_current_user tool do? +

Get the current user's information. 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_current_user? +

Register the Bangumi TV MCP Service MCP server in PolicyLayer and add a rule for get_current_user: 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_current_user? +

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

Can I rate-limit get_current_user? +

Yes. Add a rate_limit block to the get_current_user 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_current_user completely? +

Set action: deny in the PolicyLayer policy for get_current_user. 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_current_user? +

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

Free to start. No card required.

46 Bangumi TV MCP Service tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.