get_db_system
AI agents call get_db_system to retrieve information from OCI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves database system information from OCI. No description is provided, but the naming convention and context (sibling tools are all read-only queries) strongly indicate this is a simple retrieval operation. Even if it returns sensitive infrastructure details, the action itself is non-destructive read access.
From the tool's definition Tool name 'get_db_system' follows the 'get_*' pattern consistent with sibling retrieval tools (get_alarm, get_autonomous_database, get_boot_volume, get_bucket, get_budget, etc.). The 'get_' prefix indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
get_db_system. It is categorised as a Read tool in the OCI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OCI MCP Server MCP server in PolicyLayer and add a rule for get_db_system: 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 OCI MCP Server. Nothing to install.
get_db_system 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_db_system 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_db_system. 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_db_system is provided by the OCI MCP Server MCP server (jopsis/mcp-server-oci). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →