This record as markdown: /tools/eaveluo-1panel-mcp/postgresql-bind-user.md
What postgresql_bind_user does on 1Panel MCP Server
AI agents use postgresql_bind_user to create or update resources in 1Panel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 1Panel MCP Server environment.
Why postgresql_bind_user is rated Medium
Creating a PostgreSQL user is a reversible Write operation: the user account can be modified or dropped later. However, it carries high severity because an AI agent creating arbitrary database users could grant excessive permissions, expose credentials, enable unauthorized access, or create dormant accounts for lateral movement. The blast radius extends to database security posture and access control integrity.
From the tool's definition Tool name 'postgresql_bind_user' with description 'Bind/create user' indicates creation of a database user account. 'Bind' and 'create' are Write operations that modify database state by adding a new user with associated permissions and credentials.
Attacks that exploit this kind of access
The rule that runs postgresql_bind_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For postgresql_bind_user, this is the rule to start with:
postgresql_bind_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 1Panel MCP Server, apply this rule, and every postgresql_bind_user call is checked against it from then on.
Questions about postgresql_bind_user
PostgreSQL: Bind/create user. It is categorised as a Write tool in the 1Panel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for postgresql_bind_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 1Panel MCP Server. Nothing to install.
postgresql_bind_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 postgresql_bind_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 postgresql_bind_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.
postgresql_bind_user is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1Panel MCP Server, and thousands of servers like it.
This server
Across the catalogue