Search for documents using full text search in an OceanBase table. Args: table_name: Name of the table to search. full_text_search_column_name: Specify the columns to be searched in full text. full_text_search_expr: Specify the keywords or phrases to search for. other_where_clause: Other WHERE co...
AI agents call oceanbase_text_search to retrieve information from Mcp Oceanbase 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 data from an OceanBase table using full-text search with filtering options. It has no side effects—it only reads and returns results matching the search criteria. This is a classic Read operation with low risk.
From the tool's definition Tool performs 'Search for documents using full text search' with parameters for table_name, search columns, keywords, WHERE clauses, limit, and output columns. No modification, deletion, or execution capabilities are described.
Documented attack patterns abuse exactly the kind of access oceanbase_text_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Oceanbase, and nothing reaches the server without passing your rules. This is the rule we recommend for oceanbase_text_search:
{
"version": "1",
"default": "deny",
"tools": {
"oceanbase_text_search": {}
}
}oceanbase_text_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for documents using full text search in an OceanBase table. Args: table_name: Name of the table to search. full_text_search_column_name: Specify the columns to be searched in full text. full_text_search_expr: Specify the keywords or phrases to search for. other_where_clause: Other WHERE condition query statements except full-text search. limit: Maximum number of results to return. output_column_name: columns to include in results. It is categorised as a Read tool in the Mcp Oceanbase MCP Server, which means it retrieves data without modifying state.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for oceanbase_text_search: 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 Oceanbase. Nothing to install.
oceanbase_text_search 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 oceanbase_text_search 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 oceanbase_text_search. 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.
oceanbase_text_search is provided by the Mcp Oceanbase MCP server (oceanbase/awesome-oceanbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 134 Mcp Oceanbase tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
134 Mcp Oceanbase tools catalogued and risk-classified — across an index of 42,500+ MCP servers.