oakvar_modules_dir · OakVar MCP Server MCP: Risk & Policy

WHAT IT DOES

What oakvar_modules_dir does on OakVar MCP Server

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

WHY IT NEEDS A POLICY

Why oakvar_modules_dir needs a policy

This tool can modify the modules directory path, which is a reversible configuration change affecting where OakVar loads annotation modules from. While not data deletion (Destructive) or financial impact, changing the modules directory could redirect module loading to different sources, potentially with security implications. The 'get' operation is Read-only, but the 'set' capability elevates this to Write.

From the tool's definition Tool description states 'Get or set the OakVar modules directory' - the 'set' operation indicates data modification capability that changes system configuration

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

oakvar_modules_dir Rate-limited

oakvar_modules_dir 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": {
    "oakvar_modules_dir": {
      "limits": [
        {
          "counter": "oakvar_modules_dir_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 OakVar MCP Server, so you can run agents against it safely.

FAQ

Questions about oakvar_modules_dir

What does the oakvar_modules_dir tool do? +

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

How do I enforce a policy on oakvar_modules_dir? +

Register the OakVar MCP Server MCP server in PolicyLayer and add a rule for oakvar_modules_dir: 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_modules_dir? +

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

Can I rate-limit oakvar_modules_dir? +

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

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

oakvar_modules_dir 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.