run_select
AI agents invoke run_select to trigger actions in Mcp Oracle Dba. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name 'run_select' strongly implies execution of SQL SELECT queries against an Oracle database. While the server claims to be read-only with SQL guards, executing arbitrary (or semi-arbitrary) SQL queries against a database carries Execute-level risk — a misconfigured or bypassed guard could allow broader SQL execution.
From the tool's definition Tool name 'run_select' on a server described as 'SQL-guarded' with siblings like 'explain_plan' and 'top_sql'; description is empty and uninformative.
Attacks that exploit this kind of access
run_select. It is categorised as a Execute tool in the Mcp Oracle Dba MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Oracle Dba MCP server in PolicyLayer and add a rule for run_select: 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 Mcp Oracle Dba. Nothing to install.
run_select is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_select 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 run_select. 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.
run_select is provided by the Mcp Oracle Dba MCP server (shopsmartai/mcp-oracle-dba). 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 →