tool_fit_peak · origin- MCP: Risk & Policy

WHAT IT DOES

What tool_fit_peak does on origin-MCP

AI agents invoke tool_fit_peak 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_peak needs a policy

This tool executes a computational fitting operation (auto-finds peaks, runs curve fitting algorithms) against data. It triggers external processing in Origin 2025b and produces derived results. It is not a simple read/query, nor does it irreversibly destroy data, but it actively runs a numerical computation/analysis operation whose effects depend on the input arguments, placing it in the Execute category.

From the tool's definition 'Perform multi-peak fitting on spectral/chromatography data. Auto-finds peaks and fits them with Gauss or Lorentz models.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tool_fit_peak Rate-limited

tool_fit_peak 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_peak": {
      "limits": [
        {
          "counter": "tool_fit_peak_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_peak

What does the tool_fit_peak tool do? +

Perform multi-peak fitting on spectral/chromatography data. Auto-finds peaks and fits them with Gauss or Lorentz models. 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_peak? +

Register the origin- MCP server in PolicyLayer and add a rule for tool_fit_peak: 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_peak? +

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

Can I rate-limit tool_fit_peak? +

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

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

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