Checks if the Unity Editor is connected via WebSocket.
AI agents call ping_unity to retrieve information from MCP For Unity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only checks connectivity status — it queries whether a connection exists without modifying any data or triggering any side effects. Pure read/probe operation with minimal blast radius.
From the tool's definition Checks if the Unity Editor is connected via WebSocket
Attacks that exploit this kind of access
Checks if the Unity Editor is connected via WebSocket. It is categorised as a Read tool in the MCP For Unity MCP Server, which means it retrieves data without modifying state.
Register the MCP For Unity MCP server in PolicyLayer and add a rule for ping_unity: 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 For Unity. Nothing to install.
ping_unity 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 ping_unity 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 ping_unity. 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.
ping_unity is provided by the MCP For Unity MCP server (yunuscan/mcpforunity). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →