get_vital_signs

Get patient's vital signs

Server FHIR Careplan kushagra-dutta/fhir-mcp
Category Read
Risk class Low
Parameters 00 required

What get_vital_signs does on FHIR Careplan

AI agents call get_vital_signs to retrieve information from FHIR Careplan without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_vital_signs needs a policy

This tool retrieves existing patient vital sign data from a FHIR server without creating, modifying, deleting, or executing operations. It is a straightforward data query with no side effects, matching the Read category definition.

From the tool's definition Tool name 'get_vital_signs' and description 'Get patient's vital signs' indicate a retrieval operation. The verb 'Get' and the read-only nature of vital sign queries confirm no data is modified or deleted.

Questions about get_vital_signs

What does the get_vital_signs tool do? +

Get patient's vital signs. It is categorised as a Read tool in the FHIR Careplan MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_vital_signs? +

Register the FHIR Careplan MCP server in PolicyLayer and add a rule for get_vital_signs: 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 FHIR Careplan. Nothing to install.

What risk level is get_vital_signs? +

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

Can I rate-limit get_vital_signs? +

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

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

get_vital_signs is provided by the FHIR Careplan MCP server (kushagra-dutta/fhir-mcp). 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.