AI agents call get_schema to retrieve information from Omnibase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure information retrieval tool that queries database metadata without side effects. It does not create, modify, delete, or execute operations—it only reads and returns schema information. The sibling tool 'execute_sql' handles actual data operations, distinguishing this as a safe Read operation.
From the tool's definition Tool retrieves database schema information (table names, column counts, primary keys, column details). The description explicitly indicates 'Get database schema' with no mention of modifications, deletions, or code execution.
Attacks that exploit this kind of access
Get database schema. Without tables param: returns summary (table names, column counts, PKs). With tables param: returns full column details for specified tables. It is categorised as a Read tool in the Omnibase MCP Server, which means it retrieves data without modifying state.
Register the Omnibase MCP server in PolicyLayer and add a rule for get_schema: 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 Omnibase. Nothing to install.
get_schema 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_schema 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_schema. 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_schema is provided by the Omnibase MCP server (omnibase-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 →