Get comprehensive Unity project information including render pipeline details, project path, Unity version, and platform info
AI agents call project_info to retrieve information from MCP Server for Unity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs informational queries about an existing Unity project's configuration and metadata. It retrieves data without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal—an AI agent querying project information cannot damage systems or data. This is a straightforward Read operation.
From the tool's definition Tool name 'project_info' and description 'Get comprehensive Unity project information' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access project_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Unity, and nothing reaches the server without passing your rules. This is the rule we recommend for project_info:
{
"version": "1",
"default": "deny",
"tools": {
"project_info": {}
}
} project_info 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 comprehensive Unity project information including render pipeline details, project path, Unity version, and platform info. It is categorised as a Read tool in the MCP Server for Unity MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Unity MCP server in PolicyLayer and add a rule for project_info: 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 MCP Server for Unity. Nothing to install.
project_info 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 project_info 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 project_info. 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.
project_info is provided by the MCP Server for Unity MCP server (zabaglione/mcp-server-unity). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for Unity, 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.
15 MCP Server for Unity tools catalogued and risk-classified — across an index of 43,000+ MCP servers.