AI agents invoke execute_query to trigger actions in Physionet. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes SQL queries against live biomedical datasets. Although the immediate description is empty, the server context makes clear this runs code (SQL). The severity is high because: (1) SQL execution can read, modify, or delete sensitive biomedical data depending on permissions; (2) PhysioNet contains protected health information; (3) blast radius includes data exfiltration, corruption, or service…
From the tool's definition Tool name 'execute_query' combined with server description stating it 'run SQL queries' indicates execution of arbitrary SQL against PhysioNet biomedical datasets via BigQuery.
Documented attack patterns abuse exactly the kind of access execute_query 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 execute_query:
{
"version": "1",
"default": "deny",
"tools": {
"execute_query": {
"limits": [
{
"counter": "execute_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
execute_query. It is categorised as a Execute tool in the Physionet MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Physionet MCP server in PolicyLayer and add a rule for execute_query: 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.
execute_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_query 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 execute_query. 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.
execute_query 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.