Переименовать папку (viewfolder) в файле; счётчик (N) пересчитывается автоматически.
AI agents use rename_folder 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.
The tool modifies existing data (folder names and associated counters) reversibly without deleting data or executing arbitrary code. This is a write operation on structured project data. Severity is medium because renaming folders could affect project organization and references, but the operation is reversible through another rename.
From the tool's definition Tool description states 'Rename folder (viewfolder) in file' and 'counter (N) is recalculated automatically', indicating modification of existing folder metadata within Navisworks viewpoint XML files.
Attacks that exploit this kind of access
Переименовать папку (viewfolder) в файле; счётчик (N) пересчитывается автоматически. 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.
Register the Navisworks Viewpoints MCP server in PolicyLayer and add a rule for rename_folder: 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.
rename_folder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rename_folder 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.
Set action: deny in the PolicyLayer policy for rename_folder. 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.
rename_folder 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →