AI agents call get_studies_by_keyword to retrieve information from ClinicalTrials MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves clinical trial information based on keyword search parameters. It performs a query operation with no side effects—it does not create, modify, delete, or execute actions on the system. The blast radius of misuse is minimal: an agent could retrieve irrelevant or sensitive trial data, but cannot alter records or perform destructive operations. Read category is appropriate.
From the tool's definition Tool name 'get_studies_by_keyword' paired with server context describing search and retrieval of clinical trial data from ClinicalTrials.gov. Sibling tools confirm this server is for querying and accessing trial metadata.
Documented attack patterns abuse exactly the kind of access get_studies_by_keyword gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ClinicalTrials MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_studies_by_keyword:
{
"version": "1",
"default": "deny",
"tools": {
"get_studies_by_keyword": {}
}
}get_studies_by_keyword is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_studies_by_keyword. It is categorised as a Read tool in the ClinicalTrials MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ClinicalTrials MCP Server MCP server in PolicyLayer and add a rule for get_studies_by_keyword: 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 ClinicalTrials MCP Server. Nothing to install.
get_studies_by_keyword 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 get_studies_by_keyword 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 get_studies_by_keyword. 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.
get_studies_by_keyword is provided by the ClinicalTrials MCP Server MCP server (jackkuo666/clinicaltrials-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ClinicalTrials MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 ClinicalTrials MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.