scene_rename

What scene_rename does on Mcp Anything

AI agents use scene_rename to create or update resources in Mcp Anything, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Anything environment.

Why scene_rename is rated Medium

Renaming is a write operation that modifies metadata/properties but is reversible and has no destructive effects. Without description details, confidence is moderate. The 'scene' prefix indicates this operates on scene data structures in what appears to be a graphics/animation framework, making it Write rather than Read (which would be query-only) or Execute (which would trigger external commands).

From the tool's definition Tool name 'scene_rename' indicates renaming operations on scene objects; context shows animation/graphics tools (animation_*, camera_*, build_*) suggesting a graphics/3D engine environment where renaming is a reversible modification operation.

The rule that runs scene_rename safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scene_rename, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scene_rename": {
      "limits": [
        {
          "counter": "scene_rename_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about scene_rename