manage_sql_keys | PolicyLayer

WHAT IT DOES

What manage_sql_keys does on Thales CipherTrust Data Security Platform CAKM MCP Server

AI agents use manage_sql_keys to create or update resources in Thales CipherTrust Data Security Platform CAKM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Thales CipherTrust Data Security Platform CAKM MCP Server environment.

WHY IT NEEDS A POLICY

Why manage_sql_keys needs a policy

The tool manages encryption keys for SQL Server databases—a critical security control. While the description is empty, the name and server context indicate this performs reversible operations on keys (creation, modification, rotation, or configuration changes). Key rotation and management are Write operations.

From the tool's definition Tool name 'manage_sql_keys' combined with server context showing it operates on 'database encryption key operations' for SQL Server via CipherTrust CAKM.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_sql_keys Rate-limited

manage_sql_keys 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_sql_keys": {
      "limits": [
        {
          "counter": "manage_sql_keys_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Thales CipherTrust Data Security Platform CAKM MCP Server, so you can run agents against it safely.

FAQ

Questions about manage_sql_keys

What does the manage_sql_keys tool do? +

manage_sql_keys. It is categorised as a Write tool in the Thales CipherTrust Data Security Platform CAKM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_sql_keys? +

Register the Thales CipherTrust Data Security Platform CAKM MCP Server MCP server in PolicyLayer and add a rule for manage_sql_keys: 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 Thales CipherTrust Data Security Platform CAKM MCP Server. Nothing to install.

What risk level is manage_sql_keys? +

manage_sql_keys is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manage_sql_keys? +

Yes. Add a rate_limit block to the manage_sql_keys 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 manage_sql_keys completely? +

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

manage_sql_keys is provided by the Thales CipherTrust Data Security Platform CAKM MCP Server MCP server (sanyambassi/thales-cdsp-cakm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.