Get list of mysql users
AI agents call get_recent_users to retrieve information from DatabaseMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries a list of MySQL users with no side effects. It matches the Read category definition: retrieves or queries data; no side effects (search, list, get, fetch). The severity is low because user list enumeration, while informative to an attacker, does not directly compromise data integrity or cause destructive effects.
From the tool's definition Tool name 'get_recent_users' and description 'Get list of mysql users' indicate a query operation that retrieves user information without modification.
Attacks that exploit this kind of access
Get list of mysql users. It is categorised as a Read tool in the DatabaseMCP MCP Server, which means it retrieves data without modifying state.
Register the Database MCP server in PolicyLayer and add a rule for get_recent_users: 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 DatabaseMCP. Nothing to install.
get_recent_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_recent_users 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 get_recent_users. 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.
get_recent_users is provided by the Database MCP server (leovegasys/databasemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →