exportSceneCode

A execute tool on the Spline MCP server.

SERVERSpline MCP Server SOURCEaydinfer/spline-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aydinfer-spline-mcp-server/exportscenecode.md

WHAT IT DOES

What exportSceneCode does on Spline MCP Server

AI agents invoke exportSceneCode to trigger actions in Spline MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why exportSceneCode is rated High

The tool name suggests it exports scene code from Spline, which is an external operation that triggers a file/code export process. The server description explicitly mentions 'exporting scenes' as a supported operation. However, the description is empty, lowering confidence.

From the tool's definition Tool name 'exportSceneCode' on a server that 'enabling operations like exporting scenes' through the Spline 3D design tool.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs exportSceneCode safely

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

exportSceneCode Rate-limited

exportSceneCode stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "exportSceneCode": {
      "limits": [
        {
          "counter": "exportscenecode_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spline MCP Server, apply this rule, and every exportSceneCode call is checked against it from then on.

FAQ

Questions about exportSceneCode

What does the exportSceneCode tool do? +

exportSceneCode is a execute tool on the Spline MCP Server MCP server. It is categorised as a Execute tool in the Spline MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on exportSceneCode? +

Register the Spline MCP Server MCP server in PolicyLayer and add a rule for exportSceneCode: 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 Spline MCP Server. Nothing to install.

What risk level is exportSceneCode? +

exportSceneCode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit exportSceneCode? +

Yes. Add a rate_limit block to the exportSceneCode 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 exportSceneCode completely? +

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

exportSceneCode is provided by the Spline MCP Server MCP server (aydinfer/spline-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Spline MCP Server, and thousands of servers like it.

This server

All 145 Spline MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →