getScenes
A read tool on the Spline MCP server.
This record as markdown: /tools/aydinfer-spline-mcp-server/getscenes.md
What getScenes does on Spline MCP Server
AI agents call getScenes to retrieve information from Spline MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getScenes is rated Low
The 'get' prefix conventionally denotes retrieval without side effects. Given the Spline context (a 3D design tool), getScenes most likely queries and returns available scenes or scene metadata. This is a read operation with no capacity to modify, delete, or execute external code. Confidence is reduced slightly due to empty description, but the naming pattern and server context provide strong indicators.
From the tool's definition Tool name 'getScenes' indicates a retrieval operation. The server description mentions 'exporting scenes' and interaction with a 3D design tool, suggesting this fetches scene data without modification.
Attacks that exploit this kind of access
The rule that runs getScenes 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 getScenes, this is the rule to start with:
getScenes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Spline MCP Server, apply this rule, and every getScenes call is checked against it from then on.
Questions about getScenes
getScenes is a read tool on the Spline MCP Server MCP server. It is categorised as a Read tool in the Spline MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Spline MCP Server MCP server in PolicyLayer and add a rule for getScenes: 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.
getScenes 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 getScenes 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 getScenes. 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.
getScenes 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.
More on Spline MCP Server, and thousands of servers like it.
This server
Across the catalogue