Read the contents of a file from the Unity project. Paths are relative to the project
AI agents call read_file to retrieve information from Unity MCP Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file contents without side effects. It does not create, modify, delete, or execute any code. While the Unity project context includes sensitive data (scenes, settings, code), read-only access to project files poses minimal risk compared to tools like execute_editor_command or edit_file on the same server. Classification as Read is appropriate.
From the tool's definition Tool name is 'read_file' and description states 'Read the contents of a file from the Unity project.' The verb 'read' and explicit statement of reading file contents indicate data retrieval with no modification or execution.
Documented attack patterns abuse exactly the kind of access read_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for read_file:
{
"version": "1",
"default": "deny",
"tools": {
"read_file": {}
}
}read_file 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.
Read the contents of a file from the Unity project. Paths are relative to the project. It is categorised as a Read tool in the Unity MCP Integration MCP Server, which means it retrieves data without modifying state.
Register the Unity MCP Integration MCP server in PolicyLayer and add a rule for read_file: 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 Integration. Nothing to install.
read_file 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 read_file 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 read_file. 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.
read_file is provided by the Unity MCP Integration MCP server (quazaai/unitymcpintegration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Unity MCP Integration tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Unity MCP Integration tools catalogued and risk-classified — across an index of 42,500+ MCP servers.