Check how your genes affect a medication. Supports brand names (
AI agents call check_medication to retrieve information from Openpgx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pharmacogenomic information based on user-provided medication and genetic data. It performs a lookup or analysis query without creating, modifying, deleting data, or triggering external side effects. The action is informational (checking/analyzing), characteristic of Read category operations.
From the tool's definition Tool name 'check_medication' and description 'Check how your genes affect a medication' indicates a query/lookup operation.
Documented attack patterns abuse exactly the kind of access check_medication gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Openpgx, and nothing reaches the server without passing your rules. This is the rule we recommend for check_medication:
{
"version": "1",
"default": "deny",
"tools": {
"check_medication": {}
}
} check_medication 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 how your genes affect a medication. Supports brand names (. It is categorised as a Read tool in the Openpgx MCP Server, which means it retrieves data without modifying state.
Register the Openpgx MCP server in PolicyLayer and add a rule for check_medication: 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 Openpgx. Nothing to install.
check_medication 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_medication 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_medication. 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_medication is provided by the Openpgx MCP server (open-pgx/openpgx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Openpgx, 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.
15 Openpgx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.