Find game objects in the scene by tag.
AI agents call find_objects_by_tag to retrieve information from Unity MCP with Ollama Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves game objects matching a specified tag. It is a read-only operation that does not create, modify, delete, or execute external commands. The only potential risk is information disclosure if sensitive object data is exposed, but this is minimal in a development context where the user already has editor access.
From the tool's definition Tool name 'find_objects_by_tag' and description 'Find game objects in the scene by tag' indicate a query/retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access find_objects_by_tag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP with Ollama Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for find_objects_by_tag:
{
"version": "1",
"default": "deny",
"tools": {
"find_objects_by_tag": {}
}
} find_objects_by_tag 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.
Find game objects in the scene by tag. It is categorised as a Read tool in the Unity MCP with Ollama Integration MCP Server, which means it retrieves data without modifying state.
Register the Unity MCP with Ollama Integration MCP server in PolicyLayer and add a rule for find_objects_by_tag: 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 with Ollama Integration. Nothing to install.
find_objects_by_tag 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 find_objects_by_tag 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 find_objects_by_tag. 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.
find_objects_by_tag is provided by the Unity MCP with Ollama Integration MCP server (zundamonnovrchatkaisetu/unity-mcp-ollama). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Unity MCP with Ollama Integration, 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.
37 Unity MCP with Ollama Integration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.