AI agents call has_collection 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.
Based on the tool name 'has_collection', this appears to be a read-only operation that checks whether a collection exists, returning a boolean result. It retrieves state information without modifying, deleting, or executing external operations. The empty description reduces confidence slightly, but the naming convention strongly suggests a non-destructive lookup operation.
From the tool's definition Tool name is 'has_collection' which suggests a check or query operation. Description is empty, so assessment relies on the naming convention. The 'has_' prefix typically indicates a boolean check or existence query with no side effects.
Documented attack patterns abuse exactly the kind of access has_collection 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 has_collection:
{
"version": "1",
"default": "deny",
"tools": {
"has_collection": {}
}
}has_collection 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.
has_collection. 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 has_collection: 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.
has_collection 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 has_collection 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 has_collection. 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.
has_collection 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.