Search for semantically similar document chunks using Google Gemini embeddings and vector similarity
AI agents call semanticSearchGoogle to retrieve information from Medical MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/query operation retrieving similar document chunks based on semantic similarity. It has no side effects — it reads from a vector index. Severity is medium because the underlying data is sensitive medical documents; a misconfigured or over-broad query could expose patient records to unintended contexts.
From the tool's definition "Search for semantically similar document chunks using Google Gemini embeddings and vector similarity"
Attacks that exploit this kind of access
Search for semantically similar document chunks using Google Gemini embeddings and vector similarity. It is categorised as a Read tool in the Medical MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Medical MCP Server MCP server in PolicyLayer and add a rule for semanticSearchGoogle: 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 Medical MCP Server. Nothing to install.
semanticSearchGoogle 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 semanticSearchGoogle 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 semanticSearchGoogle. 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.
semanticSearchGoogle is provided by the Medical MCP Server MCP server (kalyankumarkonduru/mcp-server). 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 →