Read the start of an Avizo .hx script and summarize common commands.
AI agents call inspect_hx_script to retrieve information from Avizo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and summarizes information from existing `.hx` scripts without creating, modifying, deleting, or executing them. It is a query/inspection operation with no side effects, fitting the Read category. Severity is low because exposure of script contents poses minimal direct risk to the system.
From the tool's definition Tool name 'inspect_hx_script' and description 'Read the start of an Avizo `.hx` script and summarize common commands' explicitly indicates read-only inspection of script content with no modification or execution.
Attacks that exploit this kind of access
Read the start of an Avizo .hx script and summarize common commands. It is categorised as a Read tool in the Avizo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Avizo MCP Server MCP server in PolicyLayer and add a rule for inspect_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.
inspect_hx_script 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 inspect_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 inspect_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.
inspect_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 →