analyze_script
AI agents invoke analyze_script to trigger actions in Metis Public Health. 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.
The name 'analyze_script' most likely involves running or processing a script. Even if it only performs static analysis, the word 'script' combined with 'analyze' in an MCP context raises the possibility of code execution. The empty description lowers confidence, but the most severe plausible interpretation is Execute. Severity is high given potential for arbitrary code execution if misused.
From the tool's definition Tool name 'analyze_script' suggests execution or analysis of a script; description is empty and uninformative.
Attacks that exploit this kind of access
analyze_script. It is categorised as a Execute tool in the Metis Public Health MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for analyze_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 Metis Public Health. Nothing to install.
analyze_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 analyze_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 analyze_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.
analyze_script is provided by the Metis Public Health MCP server (sveritg/metis_ph). 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 →