AI agents call get_practitioner to retrieve information from Healow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves practitioner information from a FHIR R4 API. The verb 'Read' and the pattern of fetching a resource by identifier are characteristic of Read category operations. While the data comes from a healthcare system, this is a simple query with no side effects, making it low severity. Confidence is high due to explicit 'Read' language in the description.
From the tool's definition Tool name 'get_practitioner' and description 'Read a Practitioner resource by id' explicitly indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Read a Practitioner resource by id. It is categorised as a Read tool in the Healow MCP Server, which means it retrieves data without modifying state.
Register the Healow MCP server in PolicyLayer and add a rule for get_practitioner: 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 Healow. Nothing to install.
get_practitioner 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_practitioner 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_practitioner. 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_practitioner is provided by the Healow MCP server (voysi-ia/healow-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 →