trial_locations_getter
AI agents call trial_locations_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.
Based on the name 'trial_locations_getter' and context from the sibling tools (which include search, browse, check, and compare functions suggesting data retrieval patterns), this appears to be a read operation that queries trial location data from sources like ClinicalTrials.gov. The 'getter' suffix strongly suggests data retrieval without side effects.
From the tool's definition Tool name 'trial_locations_getter' indicates retrieval of trial location information. The name includes 'getter', a common pattern for read operations that retrieve or query data without modification.
Attacks that exploit this kind of access
trial_locations_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 trial_locations_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.
trial_locations_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 trial_locations_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 trial_locations_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.
trial_locations_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 →