AI agents call read_attachment to retrieve information from Smart EHR MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite empty description, the naming convention 'read_attachment' in the context of an EHR system indicates retrieval of patient-related attachments (documents, images, reports) without side effects.
From the tool's definition Tool name 'read_attachment' indicates data retrieval with no modification. Part of server that 'allowing secure searching, querying, and analysis of patient data.' Sibling tools (echo, eval_record, grep_record, query_record, read_resource) are all Read…
Documented attack patterns abuse exactly the kind of access read_attachment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Smart EHR MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for read_attachment:
{
"version": "1",
"default": "deny",
"tools": {
"read_attachment": {}
}
}read_attachment is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
read_attachment. It is categorised as a Read tool in the Smart EHR MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Smart EHR MCP Server MCP server in PolicyLayer and add a rule for read_attachment: 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 Smart EHR MCP Server. Nothing to install.
read_attachment 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 read_attachment 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 read_attachment. 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.
read_attachment is provided by the Smart EHR MCP Server MCP server (jmandel/health-record-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Smart EHR MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Smart EHR MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.