Generate VPC data using mrgsolve + vpc R package. No NONMEM needed. Requires observed data and model.
AI agents invoke generate_vpc_data 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 simulation code via mrgsolve and the vpc R package to generate VPC (Visual Predictive Check) data. It triggers external computational processes whose outputs depend on the provided model and data arguments. It does not merely read existing data but actively runs simulations, placing it in the Execute category.
From the tool's definition 'Generate VPC data using mrgsolve + vpc R package' — triggers external R package execution (mrgsolve simulation and vpc computation); 'No NONMEM needed' confirms it runs an alternative simulation engine
Documented attack patterns abuse exactly the kind of access generate_vpc_data 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 generate_vpc_data:
{
"version": "1",
"default": "deny",
"tools": {
"generate_vpc_data": {
"limits": [
{
"counter": "generate_vpc_data_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}generate_vpc_data 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.
Generate VPC data using mrgsolve + vpc R package. No NONMEM needed. Requires observed data and model. 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 generate_vpc_data: 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.
generate_vpc_data 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 generate_vpc_data 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 generate_vpc_data. 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.
generate_vpc_data 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.