mysql_security_encryption_status

Get Transparent Data Encryption (TDE) and keyring status.

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-security-encryption-status.md

What mysql_security_encryption_status does on Mysql Mcp

AI agents call mysql_security_encryption_status to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why mysql_security_encryption_status is rated Low

This tool retrieves and reports the current Transparent Data Encryption (TDE) and keyring configuration status. It has no side effects—it only queries existing security metadata. This is a typical Read operation: gathering information about system configuration to support security auditing and compliance monitoring. No data is modified, deleted, or executed.

From the tool's definition Tool name contains 'status' and description states 'Get...status', indicating a read-only query operation that retrieves encryption configuration information without modification or execution of arbitrary code.

Questions about mysql_security_encryption_status

What does the mysql_security_encryption_status tool do? +

Get Transparent Data Encryption (TDE) and keyring status. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_security_encryption_status? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_security_encryption_status: 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 Mysql Mcp. Nothing to install.

What risk level is mysql_security_encryption_status? +

mysql_security_encryption_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mysql_security_encryption_status? +

Yes. Add a rate_limit block to the mysql_security_encryption_status 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.

How do I block mysql_security_encryption_status completely? +

Set action: deny in the PolicyLayer policy for mysql_security_encryption_status. 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.

What MCP server provides mysql_security_encryption_status? +

mysql_security_encryption_status is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mysql, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mysql's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.