move_views · Navisworks Viewpoints MCP: Risk & Policy

WHAT IT DOES

What move_views does on Navisworks Viewpoints

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

WHY IT NEEDS A POLICY

Why move_views needs a policy

Moving views between folders modifies the organization and metadata of the Navisworks viewpoint file structure, but does not irreversibly delete data or execute arbitrary code. This is a reversible write operation that reorganizes existing data.

From the tool's definition Tool description indicates moving/transferring viewpoints ('Перенести <view> по точным именам между папками') between folders within a file, which constitutes modification of data structure and relationships.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_views Rate-limited

move_views 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": {
    "move_views": {
      "limits": [
        {
          "counter": "move_views_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 Navisworks Viewpoints, so you can run agents against it safely.

FAQ

Questions about move_views

What does the move_views tool do? +

Перенести <view> по точным именам между папками одного файла. It is categorised as a Write tool in the Navisworks Viewpoints MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_views? +

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

What risk level is move_views? +

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

Can I rate-limit move_views? +

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

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

move_views is provided by the Navisworks Viewpoints MCP server (mikhalchankasm/navisworks-viewpoints-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.