Launch Avizo or AvizoToGo with a .hx script path.
AI agents invoke run_hx_script to trigger actions in Avizo MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
run_hx_script executes code (Avizo HyperScript) whose effects are determined by the script content passed as an argument. This is a classic Execute pattern: the tool triggers external operations (Avizo workflows, image processing, data transformations) with side effects that depend entirely on what the supplied `.hx` script does.
From the tool's definition Tool description states it 'Launch[es] Avizo or AvizoToGo with a `.hx` script path', indicating execution of arbitrary scripts in a specialized application environment.
Attacks that exploit this kind of access
Launch Avizo or AvizoToGo with a .hx script path. It is categorised as a Execute tool in the Avizo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Avizo MCP Server MCP server in PolicyLayer and add a rule for run_hx_script: 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.
run_hx_script is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_hx_script 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 run_hx_script. 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.
run_hx_script 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 →