Get credentials for a MySQL database instance
AI agents call get_mysql_credentials to retrieve information from Linode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves sensitive database credentials. While it is a Read operation (no data modification), the severity is high because compromised database credentials enable unauthorized access to potentially sensitive data and systems. The blast radius depends on how widely those credentials are used and what data the database contains, but exposure of database credentials is a significant security concern.
From the tool's definition Tool name 'get_mysql_credentials' and description 'Get credentials for a MySQL database instance' indicate retrieval of authentication data without modification.
Documented attack patterns abuse exactly the kind of access get_mysql_credentials gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_mysql_credentials:
{
"version": "1",
"default": "deny",
"tools": {
"get_mysql_credentials": {}
}
}get_mysql_credentials is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get credentials for a MySQL database instance. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for get_mysql_credentials: 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 Linode MCP Server. Nothing to install.
get_mysql_credentials 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_mysql_credentials 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_mysql_credentials. 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_mysql_credentials is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Linode 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.
416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.