Run a statistical analysis on the current dataset.
AI agents invoke jamovi_run_analysis to trigger actions in jamovi MCP. 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.
This tool executes code/operations on a running jamovi engine process. While the analysis itself is not destructive (results do not irreversibly delete data), the capability to run arbitrary analyses with caller-controlled parameters represents a code execution risk. An AI agent could be misled into running computationally expensive, resource-intensive, or otherwise harmful analyses.
From the tool's definition The tool description states it will "Run a statistical analysis on the current dataset." Running an analysis is an Execute action that triggers external operations (statistical computations via the jamovi engine) whose effects depend on which analysis type…
Attacks that exploit this kind of access
Run a statistical analysis on the current dataset. It is categorised as a Execute tool in the jamovi MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the jamovi MCP server in PolicyLayer and add a rule for jamovi_run_analysis: 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 jamovi MCP. Nothing to install.
jamovi_run_analysis 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 jamovi_run_analysis 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 jamovi_run_analysis. 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.
jamovi_run_analysis is provided by the jamovi MCP server (yjm110517/jamovi-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 →