getStates

A read tool on the Spline MCP server.

SERVERSpline MCP Server SOURCEaydinfer/spline-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What getStates does on Spline MCP Server

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

RISK

Why getStates is rated Low

The 'get' prefix strongly indicates a read operation that queries or retrieves data. Without evidence of side effects (no write, delete, execute, or financial operations implied), this falls into the Read category. Low severity because retrieving state data poses minimal risk even if misused—it cannot corrupt, delete, or execute code.

From the tool's definition Tool name 'getStates' suggests retrieval of state data. The description is empty, but context from sibling tools (addHanaState, addHanaInteraction, addMaterialLayer) indicates this server manages Spline 3D scene properties and animations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getStates 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 getStates, this is the rule to start with:

getStates Allowed

getStates is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getStates": {}
  }
}

ALLOW ONLY 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 getStates call is checked against it from then on.

FAQ

Questions about getStates

What does the getStates tool do? +

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

How do I enforce a policy on getStates? +

Register the Spline MCP Server MCP server in PolicyLayer and add a rule for getStates: 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 getStates? +

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

Can I rate-limit getStates? +

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

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

getStates 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →