AI agents call pgx_consultation to retrieve information from Pgx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the server's purpose (pharmacogenomics analysis and variant clinical significance) and the pattern of sibling tools which are all read/lookup operations, pgx_consultation most likely retrieves or queries clinical consultation data without modifying or executing operations. The empty description reduces confidence slightly, but contextual evidence from related tools strongly suggests a Read classification.
From the tool's definition Tool name 'pgx_consultation' and server context indicate querying pharmacogenomics data. The description is empty, but sibling tools like 'lookup_variant_clinvar', 'get_dosing_guideline', and 'get_drug_gene_interactions' are all Read operations that retrieve…
Attacks that exploit this kind of access
pgx_consultation. It is categorised as a Read tool in the Pgx MCP Server, which means it retrieves data without modifying state.
Register the Pgx MCP server in PolicyLayer and add a rule for pgx_consultation: 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 Pgx. Nothing to install.
pgx_consultation 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 pgx_consultation 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 pgx_consultation. 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.
pgx_consultation is provided by the Pgx MCP server (julius-schmidt/mcp-pharmacogenomics). 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 →