clinical_guidelines
AI agents call clinical_guidelines to retrieve information from MCP Healthcare Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve clinical guidelines from medical databases (PubMed, CMS, etc.). Clinical guidelines are informational reference materials used to inform medical decision-making. Retrieving guidelines has no side effects—it does not modify, delete, execute code, or trigger financial transactions. It falls squarely in the Read category.
From the tool's definition Tool name 'clinical_guidelines' combined with server context indicating 'query databases like openFDA, PubMed, and CMS for pharmaceutical and clinical information.' The tool name and server functionality suggest data retrieval operations.
Attacks that exploit this kind of access
clinical_guidelines. It is categorised as a Read tool in the MCP Healthcare Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Healthcare Server MCP server in PolicyLayer and add a rule for clinical_guidelines: 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 MCP Healthcare Server. Nothing to install.
clinical_guidelines 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 clinical_guidelines 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 clinical_guidelines. 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.
clinical_guidelines is provided by the MCP Healthcare Server MCP server (shinegami-2002/mcp-healthcare-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 →