compute_vix_context

Server Tradeblocks tradeblocks-mcp

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What compute_vix_context does on Tradeblocks

AI agents use compute_vix_context to create or update resources in Tradeblocks — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tradeblocks environment.

WHY IT NEEDS A POLICY

Why compute_vix_context needs a policy

An AI agent can call compute_vix_context faster than any human can review — one bad instruction and it creates or modifies resources in Tradeblocks by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

compute_vix_context Rate-limited

compute_vix_context stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "compute_vix_context": {
      "limits": [
        {
          "counter": "compute_vix_context_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about compute_vix_context

What does the compute_vix_context tool do? +

Compute cross-ticker VIX context enrichment (Vol_Regime, Term_Structure_State, VIX ratios, etc.) for a date range. Reads already-enriched VIX/VIX9D/VIX3M data from market.enriched; writes to market.enriched_context. Call this AFTER ingesting all three VIX-family tickers for the date range \u2014 firing on incomplete data produces wrong values silently. No provider call \u2014 pure read-compute-write. It is categorised as a Write tool in the Tradeblocks MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on compute_vix_context? +

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

What risk level is compute_vix_context? +

compute_vix_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit compute_vix_context? +

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

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

compute_vix_context is provided by the Tradeblocks MCP server (tradeblocks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.