simulate_pk_interaction · Pharmacy MCP Server MCP

WHAT IT DOES

What simulate_pk_interaction does on Pharmacy MCP Server

AI agents invoke simulate_pk_interaction to trigger actions in Pharmacy MCP Server. 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.

WHY IT NEEDS A POLICY

Why simulate_pk_interaction needs a policy

The tool likely runs a pharmacokinetic interaction simulation (a computational execution), consistent with the server's stated PK/DDI simulation capability. No description is provided, so confidence is reduced. Simulation tools execute models/calculations rather than simply reading stored data or writing records. No financial or destructive action is implied.

From the tool's definition Tool name 'simulate_pk_interaction' and server context mentioning 'educational PK/DDI simulation' — PK = pharmacokinetics, DDI = drug-drug interaction simulation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulate_pk_interaction Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "simulate_pk_interaction": {
      "limits": [
        {
          "counter": "simulate_pk_interaction_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pharmacy MCP Server, so you can run agents against it safely.

FAQ

Questions about simulate_pk_interaction

What does the simulate_pk_interaction tool do? +

simulate_pk_interaction. It is categorised as a Execute tool in the Pharmacy MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on simulate_pk_interaction? +

Register the Pharmacy MCP Server MCP server in PolicyLayer and add a rule for simulate_pk_interaction: 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 Pharmacy MCP Server. Nothing to install.

What risk level is simulate_pk_interaction? +

simulate_pk_interaction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit simulate_pk_interaction? +

Yes. Add a rate_limit block to the simulate_pk_interaction 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 simulate_pk_interaction completely? +

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

simulate_pk_interaction is provided by the Pharmacy MCP Server MCP server (u9401066/pharmacy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.