Low Risk

get_scene_info

Get information about the current scene.

How to control get_scene_info ↓

What get_scene_info does on Unity MCP with Ollama Integration

AI agents call get_scene_info 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.

Low Risk

Why get_scene_info needs a policy

This tool retrieves scene metadata without side effects. It queries the current state of the Unity scene but does not modify assets, execute code, delete objects, or trigger external operations. This is a classic Read operation with minimal risk if an AI agent calls it.

From the tool's definition Tool name 'get_scene_info' and description 'Get information about the current scene' indicate a retrieval operation with no modification, creation, deletion, or code execution.

Documented attack patterns abuse exactly the kind of access get_scene_info gives an agent:

How to control get_scene_info

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 get_scene_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_scene_info": {}
  }
}

get_scene_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Unity MCP with Ollama Integration — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_scene_info

What does the get_scene_info tool do? +

Get information about the current scene. It is categorised as a Read tool in the Unity MCP with Ollama Integration MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_scene_info? +

Register the Unity MCP with Ollama Integration MCP server in PolicyLayer and add a rule for get_scene_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 Unity MCP with Ollama Integration. Nothing to install.

What risk level is get_scene_info? +

get_scene_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_scene_info? +

Yes. Add a rate_limit block to the get_scene_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.

How do I block get_scene_info completely? +

Set action: deny in the PolicyLayer policy for get_scene_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.

What MCP server provides get_scene_info? +

get_scene_info 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.

Enforce policy on every Unity MCP with Ollama Integration tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.