AI agents use get_full_studies_and_save to create or update resources in ClinicalTrials MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClinicalTrials MCP Server environment.
The tool name suggests it fetches study data and saves it, likely to CSV files based on the server's context. The 'save' component implies a Write action (creating/overwriting a file). Description is empty, lowering confidence. Severity is medium as it writes local files but does not delete or execute code.
From the tool's definition Tool name 'get_full_studies_and_save' — 'save' implies writing data; sibling tools suggest CSV saving pattern (search_clinical_trials_and_save_studies_to_csv, list_saved_csv_files)
Documented attack patterns abuse exactly the kind of access get_full_studies_and_save 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_full_studies_and_save:
{
"version": "1",
"default": "deny",
"tools": {
"get_full_studies_and_save": {
"limits": [
{
"counter": "get_full_studies_and_save_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}get_full_studies_and_save stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_full_studies_and_save. It is categorised as a Write tool in the ClinicalTrials MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClinicalTrials MCP Server MCP server in PolicyLayer and add a rule for get_full_studies_and_save: 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_full_studies_and_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the get_full_studies_and_save 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_full_studies_and_save. 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_full_studies_and_save 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.