Get a list of parameters available on the current avatar.
AI agents call get_avatar_parameters to retrieve information from VRChat MCP OSC without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data (avatar parameters) without modifying state, triggering external operations, or causing irreversible changes. It is a pure read operation similar to 'get_avatar_list' and 'get_avatar_name' on the same server. The blast radius of misuse is minimal—an agent could only learn what parameters exist, not modify avatar behavior or user experience.
From the tool's definition Tool name 'get_avatar_parameters' and description 'Get a list of parameters available on the current avatar' indicate a read-only query operation that retrieves metadata about avatar configuration.
Documented attack patterns abuse exactly the kind of access get_avatar_parameters gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VRChat MCP OSC, and nothing reaches the server without passing your rules. This is the rule we recommend for get_avatar_parameters:
{
"version": "1",
"default": "deny",
"tools": {
"get_avatar_parameters": {}
}
}get_avatar_parameters 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 a list of parameters available on the current avatar. It is categorised as a Read tool in the VRChat MCP OSC MCP Server, which means it retrieves data without modifying state.
Register the VRChat MCP OSC MCP server in PolicyLayer and add a rule for get_avatar_parameters: 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 OSC. Nothing to install.
get_avatar_parameters 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_avatar_parameters 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_avatar_parameters. 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_avatar_parameters is provided by the VRChat MCP OSC MCP server (krekun/vrchat-mcp-osc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VRChat MCP OSC, 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.
12 VRChat MCP OSC tools catalogued and risk-classified — across an index of 43,000+ MCP servers.