applyForce

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/applyforce.md

WHAT IT DOES

What applyForce does on Spline MCP Server

AI agents invoke applyForce 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 applyForce is rated High

The tool name 'applyForce' suggests it triggers a physics simulation action — applying a force to a physics body in the 3D scene. This is an Execute-type operation as it triggers an external operation (physics simulation effect) whose result depends on arguments. The description is empty, which lowers confidence.

From the tool's definition Tool name 'applyForce' on a Spline 3D design server with physics capabilities (sibling tool 'addPhysicsBody' confirms physics context)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

applyForce Rate-limited

applyForce 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": {
    "applyForce": {
      "limits": [
        {
          "counter": "applyforce_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 applyForce call is checked against it from then on.

FAQ

Questions about applyForce

What does the applyForce tool do? +

applyForce 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 applyForce? +

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

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

Can I rate-limit applyForce? +

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

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

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