AI agents call read_resource 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.
This tool retrieves health records or resources from an EHR system. While the description is empty, the context—a SMART EHR MCP Server for 'secure searching, querying, and analysis of patient data'—and the 'read_' prefix clearly indicate it retrieves (reads) data without side effects.
From the tool's definition Tool name 'read_resource' combined with sibling tools (read_attachment, query_record, grep_record) that are explicitly retrieval-focused in a SMART on FHIR EHR context indicates data access without modification.
Documented attack patterns abuse exactly the kind of access read_resource 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_resource:
{
"version": "1",
"default": "deny",
"tools": {
"read_resource": {}
}
}read_resource 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_resource. 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_resource: 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_resource 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_resource 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_resource. 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_resource 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.