Low Risk

search_by_location

根据地理坐标搜索附近的临床试验。默认查询招募中且3个月内更新的30个最相关结果。

How to control search_by_location ↓

What search_by_location does on Clinical Trials MCP Server

AI agents call search_by_location to retrieve information from Clinical Trials MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_by_location needs a policy

This tool queries clinical trial data based on geographic location coordinates and returns filtered results. It has no side effects—it does not create, modify, delete, or execute external operations. It is a read-only retrieval operation and poses minimal security risk if misused by an AI agent, as the worst case is returning clinical trial information that is already publicly available.

From the tool's definition Tool performs geographic search to 'search nearby clinical trials' and returns 'the 30 most relevant results' without modifying or deleting data.

Documented attack patterns abuse exactly the kind of access search_by_location gives an agent:

How to control search_by_location

PolicyLayer is an MCP gateway — it sits between your AI agents and Clinical Trials MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_by_location:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_by_location": {}
  }
}

search_by_location is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Clinical Trials MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_by_location

What does the search_by_location tool do? +

根据地理坐标搜索附近的临床试验。默认查询招募中且3个月内更新的30个最相关结果。. It is categorised as a Read tool in the Clinical Trials MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_by_location? +

Register the Clinical Trials MCP Server MCP server in PolicyLayer and add a rule for 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 Clinical Trials MCP Server. Nothing to install.

What risk level is search_by_location? +

search_by_location is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_by_location? +

Yes. Add a rate_limit block to the 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.

How do I block search_by_location completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides search_by_location? +

search_by_location is provided by the Clinical Trials MCP Server MCP server (pancrepal-xiaoyibao/xiaoyibao-clinical-trials-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Clinical Trials MCP Server tool call.

Start from Clinical Trials 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.

3 Clinical Trials MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.