慢性肾脏病CKD分期诊断和风险评估 - 根据eGFR值和蛋白尿水平进行G分期(G1-G5)和A分期(A1-A3)。提供详细的风险分层和临床管理建议。用于CKD诊断、分期和随访管理
AI agents call diagnose_chronic_kidney_disease_stage to retrieve information from Awesome Medical without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs diagnostic staging and risk assessment of chronic kidney disease based on input values (eGFR and proteinuria). It calculates and returns a classification/recommendation — a read/query operation with no side effects, no data modification, no code execution, and no financial implications. It is a medical calculation tool similar to the other sibling tools on this server.
From the tool's definition 分期诊断和风险评估 - 根据eGFR值和蛋白尿水平进行G分期(G1-G5)和A分期(A1-A3)。提供详细的风险分层和临床管理建议
Attacks that exploit this kind of access
慢性肾脏病CKD分期诊断和风险评估 - 根据eGFR值和蛋白尿水平进行G分期(G1-G5)和A分期(A1-A3)。提供详细的风险分层和临床管理建议。用于CKD诊断、分期和随访管理. It is categorised as a Read tool in the Awesome Medical MCP Server, which means it retrieves data without modifying state.
Register the Awesome Medical MCP server in PolicyLayer and add a rule for diagnose_chronic_kidney_disease_stage: 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 Awesome Medical. Nothing to install.
diagnose_chronic_kidney_disease_stage 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 diagnose_chronic_kidney_disease_stage 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 diagnose_chronic_kidney_disease_stage. 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.
diagnose_chronic_kidney_disease_stage is provided by the Awesome Medical MCP server (shanggqm/awesome-medical-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 →