Create an Amira-Avizo .pyscro script-object skeleton and matching .rc registration.
AI agents use create_python_script_object to create or update resources in Avizo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Avizo MCP Server environment.
This tool creates new files in the Amira-Avizo system (Python script objects and registration files). File creation is a Write operation because these artifacts are reversible—they can be modified or deleted later.
From the tool's definition The tool 'create_python_script_object' creates script-object skeleton files (`.pyscro`) and matching registration files (`.rc`), which are new file artifacts that are created but reversibly modifiable.
Attacks that exploit this kind of access
Create an Amira-Avizo .pyscro script-object skeleton and matching .rc registration. It is categorised as a Write tool in the Avizo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Avizo MCP Server MCP server in PolicyLayer and add a rule for create_python_script_object: 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 Avizo MCP Server. Nothing to install.
create_python_script_object 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 create_python_script_object 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 create_python_script_object. 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.
create_python_script_object is provided by the Avizo MCP Server MCP server (songyb1998/avizo-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 →