Verify that the MCP server has an active connection to Unity Editor
AI agents call verify_connection 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 merely verifies the status of an existing connection without retrieving substantive data, modifying state, executing code, deleting resources, or moving money. It is a diagnostic check analogous to a health check or ping, placing it squarely in the Read category with low severity, as misuse cannot cause damage or unwanted changes.
From the tool's definition Tool name is 'verify_connection' and description states it checks if 'the MCP server has an active connection to Unity Editor' — a query operation with no side effects.
Documented attack patterns abuse exactly the kind of access verify_connection 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 verify_connection:
{
"version": "1",
"default": "deny",
"tools": {
"verify_connection": {}
}
}verify_connection 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.
Verify that the MCP server has an active connection to Unity Editor. 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 verify_connection: 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.
verify_connection 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 verify_connection 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 verify_connection. 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.
verify_connection 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.