Update a database user for a Cloud SQL instance. A common use case for the update_user is to grant a user the cloudsqlsuperuser role, which can provide a user with many required permissions. This tool only supports updating users to assign database roles. * This tool returns a long-running operat...
Risk signalsAccepts URL/endpoint input (host)
Part of the Mcp server.
Free to start. No card required.
AI agents use update_user to create or modify resources in Mcp. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call update_user repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"update_user": {
"limits": [
{
"counter": "update_user_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Mcp policy for all 15 tools.
These attack patterns abuse exactly the kind of access update_user gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Update a database user for a Cloud SQL instance. A common use case for the update_user is to grant a user the cloudsqlsuperuser role, which can provide a user with many required permissions. This tool only supports updating users to assign database roles. * This tool returns a long-running operation. Use the get_operation tool to poll its status until the operation completes. * Before calling the update_user tool, always check the existing configuration of the user such as the user type with list_users tool. * As a special case for MySQL, if the list_users tool returns a full email address for the iamEmail field, for example {name=test-account, iamEmail=test-account@project-id.iam.gserviceaccount.com}, then in your update_user request, use the full email address in the iamEmail field in the name field of your toolrequest. For example, name=test-account@project-id.iam.gserviceaccount.com. Key parameters for updating user roles: * database_roles: A list of database roles to be assigned to the user. * revokeExistingRoles: A boolean field (default: false) that controls how existing roles are handled. How role updates work: 1. If revokeExistingRoles is true: * Any existing roles granted to the user but NOT in the provided database_roles list will be REVOKED. * Revoking only applies to non-system roles. System roles like cloudsqliamuser etc won't be revoked. * Any roles in the database_roles list that the user does NOT already have will be GRANTED. * If database_roles is empty, then ALL existing non-system roles are revoked. 2. If revokeExistingRoles is false (default): * Any roles in the database_roles list that the user does NOT already have will be GRANTED. * Existing roles NOT in the database_roles list are KEPT. * If database_roles is empty, then there is no change to the user's roles. Examples: * Existing Roles: [roleA, roleB] * Request: database_roles: [roleB, roleC], revokeExistingRoles: true * Result: Revokes roleA, Grants roleC. User roles become [roleB, roleC]. * Request: database_roles: [roleB, roleC], revokeExistingRoles: false * Result: Grants roleC. User roles become [roleA, roleB, roleC]. * Request: database_roles: [], revokeExistingRoles: true * Result: Revokes roleA, Revokes roleB. User roles become []. * Request: database_roles: [], revokeExistingRoles: false * Result: No change. User roles remain [roleA, roleB].. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP server in PolicyLayer and add a rule for update_user: 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. Nothing to install.
update_user 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_user 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_user. 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_user is provided by the MCP server (https://sqladmin.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.