oakvar_run · OakVar MCP Server MCP: Risk & Policy

WHAT IT DOES

What oakvar_run does on OakVar MCP Server

AI agents invoke oakvar_run to trigger actions in OakVar MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why oakvar_run needs a policy

The tool executes an external annotation pipeline process rather than merely querying or retrieving data. Execution of annotation pipelines can be computationally intensive and may produce various side effects depending on the pipeline configuration and input data.

From the tool's definition Tool performs 'Run the OakVar annotation pipeline on input files' – this executes a bioinformatics processing pipeline whose behavior and output depend entirely on the input files and pipeline configuration provided by the user.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

oakvar_run Rate-limited

oakvar_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "oakvar_run": {
      "limits": [
        {
          "counter": "oakvar_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about oakvar_run

What does the oakvar_run tool do? +

Run the OakVar annotation pipeline on input files. It is categorised as a Execute tool in the OakVar MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on oakvar_run? +

Register the OakVar MCP Server MCP server in PolicyLayer and add a rule for oakvar_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 OakVar MCP Server. Nothing to install.

What risk level is oakvar_run? +

oakvar_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit oakvar_run? +

Yes. Add a rate_limit block to the oakvar_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.

How do I block oakvar_run completely? +

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

What MCP server provides oakvar_run? +

oakvar_run is provided by the OakVar MCP Server MCP server (miliyarsh/oakvar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.