Sparse Identification of Nonlinear Dynamics (SINDy). Recovers governing differential equations (dx/dt = f(x)) from time series data. Returns human-readable sparse expressions. Fast (seconds). For algebraic y = f(x) relationships without time structure, use pysr_run instead. Pricing: free tier up ...
Part of the Occam server.
Free to start. No card required.
AI agents invoke sindy_run to trigger processes or run actions in Occam. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
sindy_run can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"sindy_run": {
"limits": [
{
"counter": "sindy_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Occam policy for all 4 tools.
These attack patterns abuse exactly the kind of access sindy_run gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Sparse Identification of Nonlinear Dynamics (SINDy). Recovers governing differential equations (dx/dt = f(x)) from time series data. Returns human-readable sparse expressions. Fast (seconds). For algebraic y = f(x) relationships without time structure, use pysr_run instead. Pricing: free tier up to 100 rows and 8 variables. Beyond that, $0.05 + $0.01 per 100 extra rows + $0.01 per extra variable squared, via x402 (USDC on Base) or MPP/Stripe. MPP/Stripe adds a flat $0.35 per-transaction fee (Stripe processing), so the MPP challenge amount in a payment_required response is $0.35 higher than the x402 amount for the same base price; x402 gets the lower rate. Omit payment for free-tier requests; paid requests without a valid credential receive a payment_required result with pricing and accepted schemes. Full pricing table as structured JSON: occam://pricing Advisory limits: jobs over 500,000 rows or 50 variables are accepted but may not converge within the time budget; the response carries a top-level warning the agent should surface and treat as tentative. If feature_names is supplied, its length must equal the number of data columns; a mismatch is rejected with a validation error. Rate limit: 10 requests/hour per IP, 200/hour global, max queue depth 20 (shared with pysr_run and pysr_uncertainty). Response (success) includes equations[] (each with variable, equation, expression, expression_latex, r2), library_terms, nonzero_terms, elapsed_seconds, canonical_match (dict with system, form, variable_map, parameter_map, confidence if the discovered system matches one of Lorenz / Lotka-Volterra / Van der Pol / Duffing; null otherwise), optional warning, optional _meta (MPP receipt on paid calls). Full response and payment-required schemas: occam://tool-schemas Example request: data=[[1.0, 0.0], [0.95, -0.31], [0.81, -0.59]], t=[0.0, 0.1, 0.2], feature_names=["x", "y"], poly_degree=2, threshold=0.1 Policy: occam://privacy-policy — Citation: occam://citation-info. It is categorised as a Execute tool in the Occam MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Occam MCP server in PolicyLayer and add a rule for sindy_run: 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 Occam. Nothing to install.
sindy_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sindy_run 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 sindy_run. 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.
sindy_run is provided by the Occam MCP server (https://occam.fit/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Occam tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.