Retrieve your own VRChat user information
AI agents call vrchat_get_current_user to retrieve information from VRChat MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user profile data from VRChat without modifying, deleting, or executing external operations. The operation is limited to the authenticated user's own information, making it a standard data retrieval (Read) action with minimal security risk. Severity is low because exposure is limited to already-authenticated user data.
From the tool's definition Tool name includes 'get' and description states 'Retrieve your own VRChat user information' — both indicate a read-only operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access vrchat_get_current_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VRChat MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for vrchat_get_current_user:
{
"version": "1",
"default": "deny",
"tools": {
"vrchat_get_current_user": {}
}
}vrchat_get_current_user 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.
Retrieve your own VRChat user information. It is categorised as a Read tool in the VRChat MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VRChat MCP Server MCP server in PolicyLayer and add a rule for vrchat_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 VRChat MCP Server. Nothing to install.
vrchat_get_current_user 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 vrchat_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.
Set action: deny in the PolicyLayer policy for vrchat_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.
vrchat_get_current_user is provided by the VRChat MCP Server MCP server (sawa-zen/vrchat-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 VRChat MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 VRChat MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.