Low Risk

btc_vrp

BTC Volatility Risk Premium (DVOL minus Parkinson realized vol, 72h). Positive = sell-vol opportunity, negative = buy-vol. Returns regime (LOW/MID/HIGH) and raw audit inputs (DVOL, RV_72h, RV_6h, spot). Live (~60s cache). $0.001 USDC on Base per call.

Part of the RegimeShift server.

btc_vrp 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 REGIMESHIFT →

Free to start. No card required.

AI agents call btc_vrp to retrieve information from RegimeShift 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 btc_vrp 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": {
    "btc_vrp": {}
  }
}

See the full RegimeShift policy for all 4 tools.

Get this rule live on your own RegimeShift server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY REGIMESHIFT →

These attack patterns abuse exactly the kind of access btc_vrp 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 btc_vrp only ever does what you allow.

SECURE REGIMESHIFT →

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

What does the btc_vrp tool do? +

BTC Volatility Risk Premium (DVOL minus Parkinson realized vol, 72h). Positive = sell-vol opportunity, negative = buy-vol. Returns regime (LOW/MID/HIGH) and raw audit inputs (DVOL, RV_72h, RV_6h, spot). Live (~60s cache). $0.001 USDC on Base per call.. It is categorised as a Read tool in the RegimeShift MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on btc_vrp? +

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

What risk level is btc_vrp? +

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

Can I rate-limit btc_vrp? +

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

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

btc_vrp is provided by the RegimeShift MCP server (https://mcp.regimeshift.xyz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RegimeShift tool call.

Deterministic rules across all 4 RegimeShift 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.