AI agents call get_table_info 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.
The tool name 'get_table_info' and its position among inspection/query tools suggests it retrieves table structure and metadata. While the description is empty, the naming pattern ('get_*') and sibling tools ('get_database_schema') indicate a read-only operation that inspects but does not modify data. Blast radius is low—misuse would only expose schema information, not cause data loss or unintended execution.
From the tool's definition Tool named 'get_table_info' with sibling tools including 'execute_query', 'get_database_schema', and 'list_accessible_datasets'. The name and context indicate this retrieves table metadata/schema information rather than executing operations or modifying data.
Documented attack patterns abuse exactly the kind of access get_table_info 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 get_table_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_table_info": {}
}
}get_table_info 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.
get_table_info. 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 get_table_info: 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.
get_table_info 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 get_table_info 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 get_table_info. 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.
get_table_info 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.