Check R installation and required packages (mrgsolve, vpc, dplyr, ggplot2).
AI agents call check_r_setup to retrieve information from Nonmem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only performs diagnostic checks of the R environment and package availability. It retrieves system state information without modifying configurations, executing code, or triggering external operations. It is a read-only inspection tool, posing minimal security risk—the worst outcome is obtaining inaccurate system status information.
From the tool's definition Tool name 'check_r_setup' and description 'Check R installation and required packages' indicate a query/verification operation with no data modification or command execution.
Documented attack patterns abuse exactly the kind of access check_r_setup 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 check_r_setup:
{
"version": "1",
"default": "deny",
"tools": {
"check_r_setup": {}
}
}check_r_setup is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check R installation and required packages (mrgsolve, vpc, dplyr, ggplot2). It is categorised as a Read tool in the Nonmem MCP Server, which means it retrieves data without modifying state.
Register the Nonmem MCP server in PolicyLayer and add a rule for check_r_setup: 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.
check_r_setup 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 check_r_setup 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 check_r_setup. 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.
check_r_setup 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.