Run a one-compartment concentration-time estimate.
AI agents invoke simulate_concentration_time 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.
This tool executes a pharmacokinetic (PK) model simulation rather than performing simple read operations or data modifications. While not immediately destructive or financial, misuse could lead to harmful outcomes if an AI agent provides incorrect concentration predictions that influence clinical decisions.
From the tool's definition Tool description states 'Run a one-compartment concentration-time estimate' — the verb 'Run' indicates execution of a pharmacokinetic simulation algorithm.
Attacks that exploit this kind of access
Run a one-compartment concentration-time estimate. 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.
Register the Pharmacy MCP Server MCP server in PolicyLayer and add a rule for simulate_concentration_time: 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.
simulate_concentration_time is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the simulate_concentration_time 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 simulate_concentration_time. 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.
simulate_concentration_time 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →