AI agents use update_backup_policy 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.
The tool modifies backup policies, which are configuration settings that affect data protection and recovery mechanisms. This is a reversible Write operation (policies can be adjusted again), but carries high severity because misconfigured backup policies could compromise disaster recovery capabilities and data protection.
From the tool's definition Tool name 'update_backup_policy' indicates modification of backup configuration. The empty description provides no details to confirm scope, but backup policy changes are data modifications affecting system resilience.
Documented attack patterns abuse exactly the kind of access update_backup_policy 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 update_backup_policy:
{
"version": "1",
"default": "deny",
"tools": {
"update_backup_policy": {
"limits": [
{
"counter": "update_backup_policy_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_backup_policy 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_backup_policy. 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 update_backup_policy: 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.
update_backup_policy 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 update_backup_policy 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 update_backup_policy. 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.
update_backup_policy 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.