Update tenant parameters This interface is used to update parameters of a tenant. The caller must have update permissions on the target tenant. The caller must be authenticated through OCP application service. Args: cluster_id: The ID of the cluster that the target tenant belongs to tenant_id: Th...
AI agents use set_oceanbase_tenant_parameters to create or update resources in Mcp Oceanbase — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Oceanbase environment.
This tool modifies tenant configuration settings in OceanBase (a database system), which is a reversible Write operation. The severity is high because changing database tenant parameters can impact availability, performance, and security of database operations, though the changes can typically be reverted. The confidence is high because the name and description unambiguously describe parameter updates.
From the tool's definition Tool name 'set_oceanbase_tenant_parameters' and description 'Update tenant parameters' directly indicate modification of configuration data.
Documented attack patterns abuse exactly the kind of access set_oceanbase_tenant_parameters 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 set_oceanbase_tenant_parameters:
{
"version": "1",
"default": "deny",
"tools": {
"set_oceanbase_tenant_parameters": {
"limits": [
{
"counter": "set_oceanbase_tenant_parameters_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_oceanbase_tenant_parameters stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update tenant parameters This interface is used to update parameters of a tenant. The caller must have update permissions on the target tenant. The caller must be authenticated through OCP application service. Args: cluster_id: The ID of the cluster that the target tenant belongs to tenant_id: The ID of the target tenant parameters: Parameter list containing parameter names, values, and parameter types Returns: OCP API response data. It is categorised as a Write tool in the Mcp Oceanbase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for set_oceanbase_tenant_parameters: 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.
set_oceanbase_tenant_parameters is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_oceanbase_tenant_parameters 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 set_oceanbase_tenant_parameters. 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.
set_oceanbase_tenant_parameters 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.