Get current patient context including medications, allergies, and conditions
AI agents call getContext to retrieve information from Medical MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing patient information with no side effects. It performs a read-only operation analogous to a GET request or SELECT query. The sibling tools (addAllergy, addMedication, editMedication, discontinueMedication) all perform Write or Destructive actions, but getContext itself only retrieves state.
From the tool's definition Tool name 'getContext' and description 'Get current patient context' use the verb 'Get', which explicitly retrieves data without modifying it. The description lists only data retrieval: 'medications, allergies, and conditions'.
Attacks that exploit this kind of access
Get current patient context including medications, allergies, and conditions. It is categorised as a Read tool in the Medical MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Medical MCP Server MCP server in PolicyLayer and add a rule for getContext: 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 Medical MCP Server. Nothing to install.
getContext 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 getContext 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 getContext. 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.
getContext is provided by the Medical MCP Server MCP server (sinduja98/sample-mcp-postmessage). 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 →