Connect to comments Oracle Database to get Oracle Schema Table and Columns Comments
AI agents call create_comment_db_connection to retrieve information from OracleDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool's purpose is to retrieve schema metadata (table and column comments) from an Oracle Database. The word 'Connect' refers to establishing a database connection for reading, not modifying data. The action is purely read/query-oriented — fetching comments/metadata. Severity is low because it only accesses schema-level comments, not sensitive data rows, though credentials may be involved (hence not minimal risk).
From the tool's definition Connect to comments Oracle Database to get Oracle Schema Table and Columns Comments
Documented attack patterns abuse exactly the kind of access create_comment_db_connection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OracleDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_comment_db_connection:
{
"version": "1",
"default": "deny",
"tools": {
"create_comment_db_connection": {}
}
}create_comment_db_connection 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.
Connect to comments Oracle Database to get Oracle Schema Table and Columns Comments. It is categorised as a Read tool in the OracleDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OracleDB MCP Server MCP server in PolicyLayer and add a rule for create_comment_db_connection: 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 OracleDB MCP Server. Nothing to install.
create_comment_db_connection 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 create_comment_db_connection 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 create_comment_db_connection. 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.
create_comment_db_connection is provided by the OracleDB MCP Server MCP server (rahgadda/oracledb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 OracleDB MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 OracleDB MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.