list_accessible_datasets
AI agents call list_accessible_datasets to retrieve information from Physionet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or enumerates available datasets without modifying any data. It is a straightforward listing/discovery function with no side effects, fitting the Read category. Severity is low because even if misused, listing datasets poses minimal risk—no data is altered, deleted, or exposed beyond what an authenticated user should already have access to.
From the tool's definition Tool name 'list_accessible_datasets' indicates a retrieval operation. Server context describes 'list accessible datasets' as one of the core query/exploration functions alongside 'view schemas' and 'inspect tables', all read-only data exploration activities.
Documented attack patterns abuse exactly the kind of access list_accessible_datasets gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Physionet, and nothing reaches the server without passing your rules. This is the rule we recommend for list_accessible_datasets:
{
"version": "1",
"default": "deny",
"tools": {
"list_accessible_datasets": {}
}
}list_accessible_datasets 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.
list_accessible_datasets. It is categorised as a Read tool in the Physionet MCP Server, which means it retrieves data without modifying state.
Register the Physionet MCP server in PolicyLayer and add a rule for list_accessible_datasets: 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 Physionet. Nothing to install.
list_accessible_datasets 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 list_accessible_datasets 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 list_accessible_datasets. 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.
list_accessible_datasets is provided by the Physionet MCP server (rafiattrach/physionet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Physionet, 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.
4 Physionet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.