Get project-specific context and documentation that the team has prepared for AI agents.
AI agents call unity_get_project_context 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 pre-existing project context and documentation prepared for AI agents. It performs a read-only query operation with no capability to modify, delete, or execute external operations. The blast radius of misuse is minimal—an agent could only access documentation that has already been prepared and made available through this interface.
From the tool's definition Tool name 'unity_get_project_context' and description 'Get project-specific context and documentation' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access unity_get_project_context 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_get_project_context:
{
"version": "1",
"default": "deny",
"tools": {
"unity_get_project_context": {}
}
}unity_get_project_context 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 project-specific context and documentation that the team has prepared for AI agents. 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_get_project_context: 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_get_project_context 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_get_project_context 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_get_project_context. 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_get_project_context 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.