Low Risk

get_scene_info

Get information about the current Cinema 4D scene.

How to control get_scene_info ↓

AI agents call get_scene_info to retrieve information from Cinema4D MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and returns scene metadata without creating, modifying, deleting, or executing arbitrary operations. It is a straightforward read operation typical of scene introspection APIs. The low severity reflects minimal blast radius if misused by an AI agent—the worst outcome would be information disclosure about the current scene state.

From the tool's definition Tool name 'get_scene_info' and description 'Get information about the current Cinema 4D scene' indicate a data retrieval operation with no modification or side effects.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Cinema4D MCP Server, 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 Cinema4D MCP Server — 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.

Go deeper

What does the get_scene_info tool do? +

Get information about the current Cinema 4D scene. It is categorised as a Read tool in the Cinema4D MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_scene_info? +

Register the Cinema4D MCP Server 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 Cinema4D MCP Server. 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 Cinema4D MCP Server MCP server (ttiimmaacc/cinema4d-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cinema4D MCP Server tool call.

Deterministic rules across all 25 Cinema4D MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

25 Cinema4D MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.