get_patient_zus_upid
AI agents call get_patient_zus_upid to retrieve information from MCP FHIR Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly suggests a read operation that retrieves patient identification data. While the description is empty (lowering confidence slightly), the tool name and context within a FHIR server for 'resource management' and 'read/write access' indicate this retrieves healthcare data.
From the tool's definition Tool name 'get_patient_zus_upid' uses the verb 'get', indicating data retrieval. The ZUS UPID refers to a unique patient identifier in some healthcare systems. No description provided to contradict this.
Attacks that exploit this kind of access
get_patient_zus_upid. It is categorised as a Read tool in the MCP FHIR Server MCP Server, which means it retrieves data without modifying state.
Register the MCP FHIR Server MCP server in PolicyLayer and add a rule for get_patient_zus_upid: 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 FHIR Server. Nothing to install.
get_patient_zus_upid 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_patient_zus_upid 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_patient_zus_upid. 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_patient_zus_upid is provided by the MCP FHIR Server MCP server (mrosata/mcp-fhir). 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 →