ctgov-search-by-location
Search ClinicalTrials.gov studies by location (city, state, country or facility).
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/ctgov-search-by-location.md
What ctgov-search-by-location does on Meta Data Mcp
AI agents call ctgov-search-by-location to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ctgov-search-by-location is rated Low
This tool retrieves and queries data from ClinicalTrials.gov, a public open data API, with no side effects. It performs a read-only search filtered by geographic criteria. No data is created, modified, deleted, or at risk of unintended consequences from misuse. The blast radius of an AI agent misusing this tool is minimal—at worst, excessive queries against a public API.
From the tool's definition Tool name 'ctgov-search-by-location' and description 'Search ClinicalTrials.gov studies by location' indicate a search/query operation against public clinical trial data. No modification, deletion, execution, or financial transaction capability is described.
Attacks that exploit this kind of access
The rule that runs ctgov-search-by-location safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ctgov-search-by-location, this is the rule to start with:
ctgov-search-by-location is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every ctgov-search-by-location call is checked against it from then on.
Questions about ctgov-search-by-location
Search ClinicalTrials.gov studies by location (city, state, country or facility). It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for ctgov-search-by-location: 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 Meta Data Mcp. Nothing to install.
ctgov-search-by-location 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 ctgov-search-by-location 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 ctgov-search-by-location. 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.
ctgov-search-by-location is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue