Medium Risk

update-db-instance

Update a given RDS DB instance in the given region

How to control update-db-instance ↓

What update-db-instance does on AWS MCP Server

AI agents use update-db-instance to create or update resources in AWS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS MCP Server environment.

Medium Risk

Why update-db-instance needs a policy

This tool modifies database instance configuration (e.g., instance class, storage, engine version, backup settings) but does not delete the instance or data. Updates are reversible through subsequent updates or rollbacks.

From the tool's definition Tool name 'update-db-instance' and description 'Update a given RDS DB instance in the given region' indicate modification of existing database configuration. RDS is a critical infrastructure component.

Documented attack patterns abuse exactly the kind of access update-db-instance gives an agent:

How to control update-db-instance

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update-db-instance:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update-db-instance": {
      "limits": [
        {
          "counter": "update-db-instance_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update-db-instance 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.

  1. Create a free account and register AWS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about update-db-instance

What does the update-db-instance tool do? +

Update a given RDS DB instance in the given region. It is categorised as a Write tool in the AWS MCP Server 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-db-instance? +

Register the AWS MCP Server MCP server in PolicyLayer and add a rule for update-db-instance: 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 AWS MCP Server. Nothing to install.

What risk level is update-db-instance? +

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

Can I rate-limit update-db-instance? +

Yes. Add a rate_limit block to the update-db-instance 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-db-instance completely? +

Set action: deny in the PolicyLayer policy for update-db-instance. 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-db-instance? +

update-db-instance is provided by the AWS MCP Server MCP server (lokeswaran-aj/aws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS MCP Server tool call.

Start from AWS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

54 AWS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.