rebuild_schema_cache
AI agents invoke rebuild_schema_cache to trigger actions in Oracle MCP Server. 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 suggests this tool triggers a rebuild/refresh of a schema cache, which is an operational action (not a simple read). Rebuilding a cache involves executing a process that scans and stores schema metadata, making it an Execute-category action. It is unlikely to be destructive (cache rebuild typically overwrites old cache with fresh data, but the underlying schema is untouched).
From the tool's definition Tool name 'rebuild_schema_cache' — description is empty and uninformative.
Attacks that exploit this kind of access
rebuild_schema_cache. It is categorised as a Execute tool in the Oracle MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Oracle MCP Server MCP server in PolicyLayer and add a rule for rebuild_schema_cache: 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 MCP Server. Nothing to install.
rebuild_schema_cache 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 rebuild_schema_cache 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 rebuild_schema_cache. 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.
rebuild_schema_cache is provided by the Oracle MCP Server MCP server (zhengwanbo/oracle-mcp-server). 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 →