RECOMMENDED for remote server. Load a genome profile using a code (e.g., pgx-a7b3c) from the /upload endpoint. The user ran a curl command (from get_upload_command) in their terminal or sandbox and received this code. This is the primary way to load genome data on the remote server without readin...
AI agents call load_profile 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 sensitive personal health and genomic data (genome profiles) based on a user-provided code. While it is a read-only operation with no modifications or deletions, the data being accessed is highly sensitive PII/PHI (personal health information and genetic data).
From the tool's definition 'Load a genome profile using a code' — retrieves genetic variant and health data. Although it uses a code rather than direct file access, it returns personal health and genomic information to the AI agent for analysis.
Documented attack patterns abuse exactly the kind of access load_profile 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 load_profile:
{
"version": "1",
"default": "deny",
"tools": {
"load_profile": {}
}
}load_profile 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.
RECOMMENDED for remote server. Load a genome profile using a code (e.g., pgx-a7b3c) from the /upload endpoint. The user ran a curl command (from get_upload_command) in their terminal or sandbox and received this code. This is the primary way to load genome data on the remote server without reading file contents into context. 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 load_profile: 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.
load_profile 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 load_profile 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 load_profile. 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.
load_profile 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.