Fetch publications and references for a clinical trial.
AI agents call trial_references_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.
This tool retrieves existing bibliographic data (publications and references) associated with clinical trials from sources like ClinicalTrials.gov. It performs a query/fetch operation without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an AI agent could only retrieve reference data, which is already public in these biomedical databases.
From the tool's definition Tool name 'trial_references_getter' and description 'Fetch publications and references for a clinical trial' indicate a retrieval operation with no data modification, deletion, or external side effects.
Attacks that exploit this kind of access
Fetch publications and references for a clinical trial. 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_references_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_references_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_references_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_references_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_references_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 →