diagnose_acute_kidney_injury_stage

急性肾损伤AKI诊断和分期 - 基于KDIGO国际标准,通过肌酐变化和尿量监测判断。提供AKI Stage 1-3分期诊断。用于住院患者急性肾损伤的早期识别和严重程度评估

Server Awesome Medical shanggqm/awesome-medical-mcp-server
Category Read
Risk class Low
Parameters 00 required

What diagnose_acute_kidney_injury_stage does on Awesome Medical

AI agents call diagnose_acute_kidney_injury_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.

Why diagnose_acute_kidney_injury_stage needs a policy

This tool performs diagnostic calculation and staging (AKI Stage 1-3) based on input parameters (creatinine changes and urine output). It reads/computes a clinical score and returns a diagnosis classification — no data is written, deleted, or executed. Severity is medium because misclassification of AKI staging could influence clinical decisions for hospitalized patients.

From the tool's definition 诊断和分期 - 基于KDIGO国际标准,通过肌酐变化和尿量监测判断。提供AKI Stage 1-3分期诊断。用于住院患者急性肾损伤的早期识别和严重程度评估

Questions about diagnose_acute_kidney_injury_stage

What does the diagnose_acute_kidney_injury_stage tool do? +

急性肾损伤AKI诊断和分期 - 基于KDIGO国际标准,通过肌酐变化和尿量监测判断。提供AKI Stage 1-3分期诊断。用于住院患者急性肾损伤的早期识别和严重程度评估. It is categorised as a Read tool in the Awesome Medical MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on diagnose_acute_kidney_injury_stage? +

Register the Awesome Medical MCP server in PolicyLayer and add a rule for diagnose_acute_kidney_injury_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.

What risk level is diagnose_acute_kidney_injury_stage? +

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

Can I rate-limit diagnose_acute_kidney_injury_stage? +

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

How do I block diagnose_acute_kidney_injury_stage completely? +

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

What MCP server provides diagnose_acute_kidney_injury_stage? +

diagnose_acute_kidney_injury_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.