nci_organization_searcher
AI agents call nci_organization_searcher 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 to search and retrieve organization information from biomedical databases. Despite the empty description, the naming convention strongly implies a read-only query operation. Given the healthcare context and NCI datasources, this is a lookup/search tool returning informational results without modifying, deleting, or executing operations.
From the tool's definition Tool name 'nci_organization_searcher' suggests querying/searching organizational data from NCI (National Cancer Institute) resources; the '_searcher' suffix indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
nci_organization_searcher. 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_organization_searcher: 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_organization_searcher 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_organization_searcher 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_organization_searcher. 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_organization_searcher 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 →