Get full parsed results of a completed NONMEM run by job ID.
AI agents call get_run_results 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 performs data retrieval of pre-computed NONMEM modeling results. It has no side effects, does not execute code or commands, does not modify data, and does not delete anything. It is purely a read operation that queries and returns existing run results indexed by job ID.
From the tool's definition Tool description states 'Get full parsed results of a completed NONMEM run' — this retrieves and queries results data without modifying, executing, or deleting anything. The verb 'Get' and the absence of any modification language confirm read-only semantics.
Documented attack patterns abuse exactly the kind of access get_run_results 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 get_run_results:
{
"version": "1",
"default": "deny",
"tools": {
"get_run_results": {}
}
}get_run_results 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.
Get full parsed results of a completed NONMEM run by job ID. 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 get_run_results: 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.
get_run_results 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 get_run_results 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 get_run_results. 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.
get_run_results 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.