Run a simulation using mrgsolve (R). No NONMEM needed. Provide model code or model file path.
AI agents invoke simulate_mrgsolve to trigger actions in Nonmem. 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 R code via mrgsolve to perform simulations. While the primary purpose is legitimate pharmacometric modeling, the ability to provide arbitrary model code or load external files combined with R execution creates an Execute risk. The effects are not reversible side-effects (Write), but rather computational operations whose outcomes depend on supplied arguments.
From the tool's definition 'Run a simulation using mrgsolve (R)' indicates execution of external code/operations. The tool accepts 'model code or model file path' as input, meaning an AI agent could inject arbitrary R code to be executed.
Documented attack patterns abuse exactly the kind of access simulate_mrgsolve gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nonmem, and nothing reaches the server without passing your rules. This is the rule we recommend for simulate_mrgsolve:
{
"version": "1",
"default": "deny",
"tools": {
"simulate_mrgsolve": {
"limits": [
{
"counter": "simulate_mrgsolve_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}simulate_mrgsolve stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run a simulation using mrgsolve (R). No NONMEM needed. Provide model code or model file path. It is categorised as a Execute tool in the Nonmem MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nonmem MCP server in PolicyLayer and add a rule for simulate_mrgsolve: 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 Nonmem. Nothing to install.
simulate_mrgsolve 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 simulate_mrgsolve 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 simulate_mrgsolve. 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.
simulate_mrgsolve is provided by the Nonmem MCP server (sueinchoi/nonmem-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nonmem, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Nonmem tools catalogued and risk-classified — across an index of 43,000+ MCP servers.