AI agents call vtk_is_a_class 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.
The tool retrieves information about VTK class existence by querying the VTK API metadata. It returns a boolean result without modifying, executing, or deleting anything. The operation is purely informational and safe for an AI agent to use. All sibling tools on this server are similarly read-only (get_doc, get_info, get_methods, etc.), confirming the server's purpose is API validation and introspection only.
From the tool's definition Tool performs a lookup/query operation: 'Check if a given name is a valid VTK class. Returns true if it exists in the VTK API, false otherwise.' This is a read-only query with no side effects.
Attacks that exploit this kind of access
Check if a given name is a valid VTK class. Returns true if it exists in the VTK API, false otherwise. 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_is_a_class: 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_is_a_class 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_is_a_class 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_is_a_class. 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_is_a_class 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 →