Get patient
AI agents call get_vital_signs to retrieve information from Agent Care MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves vital signs data from patient health records without modifying, deleting, or executing operations. It is a read operation on sensitive health information. Severity is 'high' rather than 'medium' because unauthorized access to vital signs and other PHI via EMR systems could enable privacy violations, identity theft, or targeted harm to patients, despite being a read-only operation.
From the tool's definition Tool name 'get_vital_signs' and sibling tools (get_appointments, get_lab_results, get_medications_history, get_patient_*) all follow a retrieval pattern.
Attacks that exploit this kind of access
Get patient. It is categorised as a Read tool in the Agent Care MCP MCP Server, which means it retrieves data without modifying state.
Register the Agent Care 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 Agent Care MCP. Nothing to install.
get_vital_signs 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 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.
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.
get_vital_signs is provided by the Agent Care MCP server (polya20/agentcare-mcp). 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 →