Low Risk

parse_control_stream

Parse a NONMEM control stream (.ctl/.mod) into structured components: $THETA, $OMEGA, $SIGMA, $EST options, input columns, data file, and ADVAN/TRANS.

How to control parse_control_stream ↓

What parse_control_stream does on Nonmem

AI agents call parse_control_stream 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.

Low Risk

Why parse_control_stream needs a policy

This tool reads and parses a NONMEM control stream file into structured data. It only retrieves/analyzes existing file content with no side effects, modifications, or execution of code.

From the tool's definition Parse a NONMEM control stream (.ctl/.mod) into structured components

Documented attack patterns abuse exactly the kind of access parse_control_stream gives an agent:

How to control parse_control_stream

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 parse_control_stream:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "parse_control_stream": {}
  }
}

parse_control_stream is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Nonmem — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about parse_control_stream

What does the parse_control_stream tool do? +

Parse a NONMEM control stream (.ctl/.mod) into structured components: $THETA, $OMEGA, $SIGMA, $EST options, input columns, data file, and ADVAN/TRANS. It is categorised as a Read tool in the Nonmem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on parse_control_stream? +

Register the Nonmem MCP server in PolicyLayer and add a rule for parse_control_stream: 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.

What risk level is parse_control_stream? +

parse_control_stream is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit parse_control_stream? +

Yes. Add a rate_limit block to the parse_control_stream 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.

How do I block parse_control_stream completely? +

Set action: deny in the PolicyLayer policy for parse_control_stream. 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.

What MCP server provides parse_control_stream? +

parse_control_stream 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.

Enforce policy on every Nonmem tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.