Low Risk

workflow.run_liquidation_safety

Calculate the liquidation price for an isolated-margin futures position. Use when user asks "where will I get liquidated?" or "how close is my liq price?". Returns: liquidationPrice, distancePct (how far from entry).

Part of the TradingCalc MCP — Crypto Futures Math server.

workflow.run_liquidation_safety is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TRADINGCALC MCP — CRYPTO FUTURES MATH →

Free to start. No card required.

AI agents call workflow.run_liquidation_safety to retrieve information from TradingCalc MCP — Crypto Futures Math without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though workflow.run_liquidation_safety only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "workflow.run_liquidation_safety": {}
  }
}

See the full TradingCalc MCP — Crypto Futures Math policy for all 19 tools.

Get this rule live on your own TradingCalc MCP — Crypto Futures Math server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TRADINGCALC MCP — CRYPTO FUTURES MATH →

View all 19 tools →

These attack patterns abuse exactly the kind of access workflow.run_liquidation_safety gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so workflow.run_liquidation_safety only ever does what you allow.

SECURE TRADINGCALC MCP — CRYPTO FUTURES MATH →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the workflow.run_liquidation_safety tool do? +

Calculate the liquidation price for an isolated-margin futures position. Use when user asks "where will I get liquidated?" or "how close is my liq price?". Returns: liquidationPrice, distancePct (how far from entry).. It is categorised as a Read tool in the TradingCalc MCP — Crypto Futures Math MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on workflow.run_liquidation_safety? +

Register the TradingCalc MCP — Crypto Futures Math MCP server in PolicyLayer and add a rule for workflow.run_liquidation_safety: 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 TradingCalc MCP — Crypto Futures Math. Nothing to install.

What risk level is workflow.run_liquidation_safety? +

workflow.run_liquidation_safety is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit workflow.run_liquidation_safety? +

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

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

workflow.run_liquidation_safety is provided by the TradingCalc MCP — Crypto Futures Math MCP server (https://tradingcalc.io/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TradingCalc MCP — Crypto Futures Math tool call.

Deterministic rules across all 19 TradingCalc MCP — Crypto Futures Math 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.