Search ClinicalTrials.gov for recruiting trials matching a condition.
AI agents call search_clinical_trials to retrieve information from Fhir Synthetic without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about clinical trials from a public database (ClinicalTrials.gov) with no side effects. It does not create, modify, delete, or execute code. The blast radius of misuse is minimal—an agent could retrieve irrelevant or sensitive trial information, but cannot alter trial records or trigger actions. This is a straightforward Read operation with low severity.
From the tool's definition Tool name 'search_clinical_trials' and description 'Search ClinicalTrials.gov for recruiting trials matching a condition' indicate a query operation against an external public database.
Attacks that exploit this kind of access
Search ClinicalTrials.gov for recruiting trials matching a condition. It is categorised as a Read tool in the Fhir Synthetic MCP Server, which means it retrieves data without modifying state.
Register the Fhir Synthetic MCP server in PolicyLayer and add a rule for search_clinical_trials: 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 Fhir Synthetic. Nothing to install.
search_clinical_trials 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 search_clinical_trials 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 search_clinical_trials. 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.
search_clinical_trials is provided by the Fhir Synthetic MCP server (krishnakakani-github/fhir-synthetic-mcp). 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 →