Get database connection info: server time, PostgreSQL version, schema, and table count.
AI agents call database_info to retrieve information from AACT Clinical Trials MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns database metadata and system information. It does not modify data, execute arbitrary code, delete anything, or move money. The blast radius of misuse is minimal — an AI agent could only learn about the database structure but cannot alter or interact with actual trial data. Classified as Read with low severity.
From the tool's definition Tool retrieves metadata about database connection info including 'server time, PostgreSQL version, schema, and table count' — purely informational queries with no modification, execution, or deletion of data.
Documented attack patterns abuse exactly the kind of access database_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AACT Clinical Trials MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for database_info:
{
"version": "1",
"default": "deny",
"tools": {
"database_info": {}
}
}database_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 database connection info: server time, PostgreSQL version, schema, and table count. It is categorised as a Read tool in the AACT Clinical Trials MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AACT Clinical Trials MCP Server MCP server in PolicyLayer and add a rule for database_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 AACT Clinical Trials MCP Server. Nothing to install.
database_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 database_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 database_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.
database_info is provided by the AACT Clinical Trials MCP Server MCP server (navisbio/aact_clinicaltrials_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AACT Clinical Trials 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.
7 AACT Clinical Trials MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.