List all schemas (users/owners) in the database that have at least one table.
AI agents call list_schemas to retrieve information from Oracle Sqlplus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries metadata about database schemas without executing any DDL, DML, or arbitrary code. It is a passive read operation that returns schema information. The blast radius is minimal—an AI agent cannot cause damage by listing schemas. Severity is low because the information returned is typically non-sensitive metadata that is discoverable through other means.
From the tool's definition Tool name 'list_schemas' and description 'List all schemas (users/owners) in the database that have at least one table' indicate a retrieval-only operation with no modification or execution of code.
Attacks that exploit this kind of access
List all schemas (users/owners) in the database that have at least one table. It is categorised as a Read tool in the Oracle Sqlplus MCP Server, which means it retrieves data without modifying state.
Register the Oracle Sqlplus MCP server in PolicyLayer and add a rule for list_schemas: 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 Oracle Sqlplus. Nothing to install.
list_schemas 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 list_schemas 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 list_schemas. 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.
list_schemas is provided by the Oracle Sqlplus MCP server (sagar1012/oracle-sqlplus-mcp). 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 →