Parse a USD ASCII .usda file into a structured AST with prims, attributes, variants, connections, and composition arcs.
AI agents call parse_usda to retrieve information from VFX Parsers MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and parses an existing .usda file into an in-memory AST representation. It retrieves and structures data without modifying any files, consistent with a pure read/query operation. The server description explicitly states 'without modifying files'.
From the tool's definition Parse a USD ASCII .usda file into a structured AST with prims, attributes, variants, connections, and composition arcs.
Attacks that exploit this kind of access
Parse a USD ASCII .usda file into a structured AST with prims, attributes, variants, connections, and composition arcs. It is categorised as a Read tool in the VFX Parsers MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VFX Parsers MCP Server MCP server in PolicyLayer and add a rule for parse_usda: 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 VFX Parsers MCP Server. Nothing to install.
parse_usda 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 parse_usda 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 parse_usda. 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.
parse_usda is provided by the VFX Parsers MCP Server MCP server (mabaam/mcp-vfx-parsers). 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 →