Get an EditorPrefs value by key. Specify type: string (default), int, float, bool.
AI agents call unity_editorprefs_get to retrieve information from Unity 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 EditorPrefs values (Unity's editor preference storage) by key without modifying, creating, executing code, or deleting anything. It is a simple query/fetch operation that returns data. EditorPrefs in Unity typically store non-sensitive editor UI preferences and user settings, so the blast radius of misuse is minimal—worst case an agent reads editor preferences but cannot act destructively.
From the tool's definition Tool name 'unity_editorprefs_get' and description 'Get an EditorPrefs value by key' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access unity_editorprefs_get gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for unity_editorprefs_get:
{
"version": "1",
"default": "deny",
"tools": {
"unity_editorprefs_get": {}
}
}unity_editorprefs_get 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 an EditorPrefs value by key. Specify type: string (default), int, float, bool. It is categorised as a Read tool in the Unity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_editorprefs_get: 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 Unity MCP Server. Nothing to install.
unity_editorprefs_get 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 unity_editorprefs_get 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 unity_editorprefs_get. 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.
unity_editorprefs_get is provided by the Unity MCP Server MCP server (anklebreaker-studio/unity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 324 Unity MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
324 Unity MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.