AI agents call search_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 tool retrieves and queries schema metadata (table and column names and comments) without modifying data or executing operations. It is a pure read-only search function analogous to catalog inspection. Even though it is on a database server with sibling tools like execute_sql and get_schema, search_schema itself performs no side effects—it only returns filtered metadata results.
From the tool's definition Tool description explicitly states it 'Search[es] for tables and columns by keyword' and 'Returns up to 20 results ranked by relevance'. The action is a search/query operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search for tables and columns by keyword. Searches names and comments. Returns up to 20 results ranked by relevance. 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 search_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.
search_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 search_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 search_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.
search_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 →