tool_fit_nonlinear · origin- MCP: Risk & Policy

WHAT IT DOES

What tool_fit_nonlinear does on origin-MCP

AI agents invoke tool_fit_nonlinear to trigger actions in origin-MCP. 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.

WHY IT NEEDS A POLICY

Why tool_fit_nonlinear needs a policy

This tool triggers a computational fitting operation in Origin 2025b — it runs an iterative numerical algorithm (non-linear curve fitting) against data. This constitutes executing an external operation whose effects depend on the arguments provided (model choice, parameter guesses, bounds). It is not a simple read/query, and it modifies the state of the Origin session by producing fit results.

From the tool's definition Perform non-linear curve fitting... Choose from 12 models (Gauss, Lorentz, ExpDecay, Poly, Sine, etc.). Set parameter guesses, fix params, or bounds.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tool_fit_nonlinear Rate-limited

tool_fit_nonlinear 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": {
    "tool_fit_nonlinear": {
      "limits": [
        {
          "counter": "tool_fit_nonlinear_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches origin-MCP, so you can run agents against it safely.

FAQ

Questions about tool_fit_nonlinear

What does the tool_fit_nonlinear tool do? +

Perform non-linear curve fitting. Choose from 12 models (Gauss, Lorentz, ExpDecay, Poly, Sine, etc.). Set parameter guesses, fix params, or bounds. It is categorised as a Execute tool in the origin-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tool_fit_nonlinear? +

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

What risk level is tool_fit_nonlinear? +

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

Can I rate-limit tool_fit_nonlinear? +

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

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

tool_fit_nonlinear is provided by the origin- MCP server (zhang-923-ze/origin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.