update_backup_plan · Observability MCP: Risk & Policy

WHAT IT DOES

What update_backup_plan does on Observability

AI agents use update_backup_plan to create or update resources in Observability — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Observability environment.

WHY IT NEEDS A POLICY

Why update_backup_plan needs a policy

Modifying a backup plan is a Write operation—it creates or modifies data reversibly without permanently destroying resources. However, severity is high because incorrect backup plan updates could compromise data recovery capabilities, affecting critical infrastructure. The blast radius includes potential loss of recovery options for important systems if the plan is misconfigured.

From the tool's definition Tool name: 'update_backup_plan'; description: 'Updates a backup plan.' The verb 'Updates' indicates modification of existing data (backup plan configuration). This is a write operation that changes backup settings reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_backup_plan Rate-limited

update_backup_plan 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_backup_plan": {
      "limits": [
        {
          "counter": "update_backup_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Observability, so you can run agents against it safely.

FAQ

Questions about update_backup_plan

What does the update_backup_plan tool do? +

Updates a backup plan. It is categorised as a Write tool in the Observability MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_backup_plan? +

Register the Observability MCP server in PolicyLayer and add a rule for update_backup_plan: 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 Observability. Nothing to install.

What risk level is update_backup_plan? +

update_backup_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_backup_plan? +

Yes. Add a rate_limit block to the update_backup_plan 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.

How do I block update_backup_plan completely? +

Set action: deny in the PolicyLayer policy for update_backup_plan. 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.

What MCP server provides update_backup_plan? +

update_backup_plan is provided by the Observability MCP server (@google-cloud/observability-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.