nci_intervention_getter
AI agents call nci_intervention_getter to retrieve information from CzechMedMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve intervention information from biomedical databases (NCI is part of NIH/NCI cancer research resources). The 'getter' pattern and context within a healthcare MCP server connecting to biomedical sources (PubMed, ClinicalTrials.gov, OpenFDA) strongly suggest this is a read-only query operation.
From the tool's definition Tool name 'nci_intervention_getter' suggests retrieval of intervention data from NCI (National Cancer Institute) sources. The 'getter' suffix indicates a read operation that fetches or retrieves information without modification.
Attacks that exploit this kind of access
nci_intervention_getter. It is categorised as a Read tool in the CzechMedMCP MCP Server, which means it retrieves data without modifying state.
Register the CzechMed MCP server in PolicyLayer and add a rule for nci_intervention_getter: 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 CzechMedMCP. Nothing to install.
nci_intervention_getter 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 nci_intervention_getter 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 nci_intervention_getter. 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.
nci_intervention_getter is provided by the CzechMed MCP server (petrsovadina/czechmedmcp). 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 →