set_active_vmrs · ModelRisk MCP: Risk & Policy

WHAT IT DOES

What set_active_vmrs does on ModelRisk MCP

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

WHY IT NEEDS A POLICY

Why set_active_vmrs needs a policy

The 'set_' verb combined with sibling tools (get_active_workbook, get_cell, get_simulation_results) suggests this modifies the active workbook reference or model state. This is a Write operation—it changes configuration but is reversible (can set a different active model). Not Execute because it doesn't run simulations or trigger external operations; not Destructive because the change is reversible.

From the tool's definition Tool name 'set_active_vmrs' with 'set_' prefix indicates modification of state. In ModelRisk context, 'vmrs' likely refers to an internal workbook or model reference. Description is empty, limiting precision.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_active_vmrs Rate-limited

set_active_vmrs 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": {
    "set_active_vmrs": {
      "limits": [
        {
          "counter": "set_active_vmrs_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 ModelRisk MCP, so you can run agents against it safely.

FAQ

Questions about set_active_vmrs

What does the set_active_vmrs tool do? +

set_active_vmrs. It is categorised as a Write tool in the ModelRisk MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_active_vmrs? +

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

What risk level is set_active_vmrs? +

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

Can I rate-limit set_active_vmrs? +

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

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

set_active_vmrs is provided by the ModelRisk MCP server (vosesoftware/modelrisk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.