getVariable
A read tool on the Spline MCP server.
This record as markdown: /tools/aydinfer-spline-mcp-server/getvariable.md
What getVariable does on Spline MCP Server
AI agents call getVariable 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 getVariable is rated Low
The 'get' prefix strongly indicates a read operation that retrieves variable data from the Spline 3D design tool. Without evidence of side effects, data modification, or execution capabilities, this falls into the Read category. Confidence is moderate (0.7) rather than high due to the empty description, but the naming pattern is consistent with query/retrieval semantics across the sibling tool ecosystem.
From the tool's definition Tool name 'getVariable' suggests retrieval of data without modification. The description is empty, but following naming conventions, 'get' operations are non-destructive queries.
Attacks that exploit this kind of access
The rule that runs getVariable 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 getVariable, this is the rule to start with:
getVariable 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 getVariable call is checked against it from then on.
Questions about getVariable
getVariable 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 getVariable: 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.
getVariable 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 getVariable 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 getVariable. 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.
getVariable 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