Check the status and progress of a submitted NONMEM run by job ID.
AI agents call check_run_status 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 retrieves status information about a run—a pure read operation with no side effects. It does not execute code, modify data, delete anything, or commit financial transactions. The lowest severity is appropriate since status queries pose minimal risk even if called repeatedly or with incorrect job IDs.
From the tool's definition Tool name 'check_run_status' and description 'Check the status and progress of a submitted NONMEM run by job ID' indicate querying/retrieving the status of an existing run without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access check_run_status 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_run_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_run_status": {}
}
}check_run_status 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 the status and progress of a submitted 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 check_run_status: 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_run_status 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_run_status 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_run_status. 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_run_status 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.