Массово добавить префикс и/или суффикс к именам точек. Мастер не нужен.
AI agents use affix_view_names 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.
This tool modifies existing viewpoint names by prepending/appending text. It is a bulk rename operation — reversible in principle (names can be changed back), so it falls under Write. The blast radius is medium because it can modify many viewpoints at once, potentially causing confusion or data integrity issues in the Navisworks project if done incorrectly.
From the tool's definition "Массово добавить префикс и/или суффикс к именам точек" — bulk add prefix and/or suffix to viewpoint names
Attacks that exploit this kind of access
Массово добавить префикс и/или суффикс к именам точек. Мастер не нужен. 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 affix_view_names: 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.
affix_view_names 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 affix_view_names 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 affix_view_names. 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.
affix_view_names 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 →