gcp_sql_create_user
Create a user in a Cloud SQL instance
This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-sql-create-user.md
What gcp_sql_create_user does on GCP MCP Server
AI agents use gcp_sql_create_user to create or update resources in GCP MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GCP MCP Server environment.
Why gcp_sql_create_user is rated Medium
Creating a database user is a reversible Write operation that modifies the database configuration and access control state. While it does not delete data, it grants new credentials that could escalate privileges or enable unauthorized access if an AI agent misuses the tool by creating overly-permissive users or with poor credential hygiene.
From the tool's definition Tool name explicitly states 'create_user' and description confirms 'Create a user in a Cloud SQL instance'. This creates a new database user account with associated credentials and permissions.
Attacks that exploit this kind of access
The rule that runs gcp_sql_create_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GCP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gcp_sql_create_user, this is the rule to start with:
gcp_sql_create_user 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.
The button opens the PolicyLayer dashboard: create your workspace, connect GCP MCP Server, apply this rule, and every gcp_sql_create_user call is checked against it from then on.
Questions about gcp_sql_create_user
Create a user in a Cloud SQL instance. It is categorised as a Write tool in the GCP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_sql_create_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 GCP MCP Server. Nothing to install.
gcp_sql_create_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 gcp_sql_create_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 gcp_sql_create_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.
gcp_sql_create_user is provided by the GCP MCP Server MCP server (ahmedselimmansor-ctrl/gcp_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GCP MCP Server, and thousands of servers like it.
This server
Across the catalogue