AI agents call vtk_get_class_module to retrieve information from Vtkapi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about VTK class module paths. It performs a read-only lookup operation that neither modifies data, executes code, deletes anything, nor involves financial transactions. The blast radius of misuse is minimal—returning incorrect module paths would only affect the accuracy of information provided to the user, not cause operational harm.
From the tool's definition Tool returns import path information for VTK classes. The description indicates it 'returns' data without modification or execution: 'Return the vtkmodules.* import path for a given VTK class'. This is a pure lookup/retrieval operation with no side effects.
Attacks that exploit this kind of access
Return the vtkmodules.* import path for a given VTK class. It is categorised as a Read tool in the Vtkapi MCP Server, which means it retrieves data without modifying state.
Register the Vtkapi MCP server in PolicyLayer and add a rule for vtk_get_class_module: 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 Vtkapi. Nothing to install.
vtk_get_class_module is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vtk_get_class_module 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 vtk_get_class_module. 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.
vtk_get_class_module is provided by the Vtkapi MCP server (patrickoleary/vtkapi-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 →