AI agents invoke scale_tenant to trigger actions in Mcp Oceanbase. 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.
Despite the empty description, the name 'scale_tenant' combined with sibling tools that manage database infrastructure (activate_tenant, change_tenant_password, configure_cluster_connection, call_obshell_sdk) indicates this likely executes commands that trigger cluster-level operations.
From the tool's definition Tool named 'scale_tenant' with empty description; context from sibling tools (activate_tenant, change_tenant_password, configure_cluster_connection, call_obshell_sdk) suggests infrastructure operations on OceanBase database cluster.
Documented attack patterns abuse exactly the kind of access scale_tenant 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 scale_tenant:
{
"version": "1",
"default": "deny",
"tools": {
"scale_tenant": {
"limits": [
{
"counter": "scale_tenant_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} scale_tenant stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
scale_tenant. It is categorised as a Execute tool in the Mcp Oceanbase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for scale_tenant: 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.
scale_tenant 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 scale_tenant 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 scale_tenant. 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.
scale_tenant 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.