Skip to main content
Glama
sanyambassi

thales-cdsp-csm-mcp-server

by sanyambassi

manage_secrets

Create, retrieve, update, and delete static and dynamic secrets including LDAP, MySQL, and MongoDB credentials, with bulk operations and listing.

Instructions

SECRETS MANAGEMENT TOOL - Create, retrieve, update, and delete secrets

SUPPORTED ACTIONS: • create_static_secret: Create text/JSON secrets with metadata • get_static_secret_value: Retrieve secret values securely
• update: Modify secret properties and values • delete: Delete individual secrets (smart detection) • delete_items: Bulk delete multiple secrets or directories • list: List secrets in directory with type filtering • list_dynamic_secrets: List all dynamic secrets globally • create_dynamic_secret_ldap: Create LDAP dynamic secrets • create_dynamic_secret_mysql: Create MySQL dynamic secrets • create_dynamic_secret_mongodb: Create MongoDB dynamic secrets • list_shared_items: List shared secrets and items

DELETE OPERATIONS: • Individual: delete(name="/secret1") • Multiple: delete_items(items=["/secret1", "/secret2"]) • Directory: delete_items(path="/directory/")

Example: Create a database password secret

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sslNoEnable/Disable SSL for MySQL dynamic secrets
ttlNoTime to live in seconds (for dynamic secrets)
jsonNoSet output format to JSON
nameNoSecret/directory name/path (required for create_static_secret, get_static_secret_value, update, delete)
pathNoPath to list secrets from (for list action only - not used for list_dynamic_secrets)
tagsNoTags to attach to the dynamic secret
itemsNoList of item names to delete (for bulk delete). Must be an array of strings, e.g., ['/item1', '/item2']
valueNoSecret value (required for create_static_secret, optional for update)
actionYesSecret management action to perform. SUPPORTED ACTIONS: 'create_static_secret' (create text/JSON secrets), 'get_static_secret_value' (retrieve secret values), 'update' (modify secret properties), 'delete' (smart delete individual items), 'delete_items' (bulk delete multiple items or directories), 'list' (list secrets in directory with type filtering), 'list_dynamic_secrets' (list all dynamic secrets globally), 'create_dynamic_secret_ldap' (create LDAP dynamic secrets), 'create_dynamic_secret_mysql' (create MySQL dynamic secrets), 'create_dynamic_secret_mongodb' (create MongoDB dynamic secrets), 'list_shared_items' (list shared secrets/items)
formatNoSecret format: 'text', 'json', 'key-value'text
bind_dnNoBind DN for LDAP dynamic secrets
user_dnNoUser DN for LDAP dynamic secrets
versionNoVersion to delete (-1 for all versions)
group_dnNoGroup DN for temporary user addition
ldap_urlNoLDAP Server URL for dynamic secrets
metadataNoAdditional metadata in JSON format
new_nameNoNew name for the secret (for update action)
passwordNoPassword for the secret
user_ttlNoUser TTL for dynamic secrets (default: 60m)60m
usernameNoUsername for the secret
filter_byNoFilter secrets by pattern (for list action only - not used for list_dynamic_secrets)
inject_urlNoWebsite context URLs
mysql_hostNoMySQL host for dynamic secrets127.0.0.1
mysql_portNoMySQL port for dynamic secrets3306
auto_rotateNoEnable auto-rotation (for rotated secrets)
descriptionNoSecret description
secret_typeNoSecret type: 'static' (for create_static_secret action only). For dynamic secrets, use specific actions: create_dynamic_secret_ldap/mysql/mongodbstatic
target_nameNoTarget name to associate with dynamic secret
change_eventNoTrigger an event when a secret value changed
custom_fieldNoCustom key-value pairs
dynamic_typeNoDynamic secret type (for dynamic secrets)
ldap_ca_certNoCA Certificate File Content for LDAP
max_versionsNoMaximum number of versions to keep
mongodb_nameNoMongoDB name for dynamic secrets
mysql_dbnameNoMySQL database name for dynamic secrets
secret_typesNoFilter by secret types within the specified directory. Options: ['static-secret', 'dynamic-secret', 'rotated-secret']. Leave empty to include all types. Note: This filters within the specified path, unlike 'list_dynamic_secrets' which searches globally.
accessibilityNoAccessibility levelregular
host_providerNoHost provider type [explicit/target]explicit
mongodb_rolesNoMongoDB roles (default: [])[]
provider_typeNoProvider type for LDAP dynamic secrets
db_server_nameNoServer name for certificate verification
delete_in_daysNoSoft delete retention period in days
mysql_passwordNoMySQL password for dynamic secrets
mysql_usernameNoMySQL username for dynamic secrets
protection_keyNoProtection key name
user_attributeNoUser attribute for LDAP dynamic secrets
multiline_valueNoWhether the provided value is multiline
password_lengthNoLength of password to be generated for dynamic secrets
ssl_certificateNoSSL connection certificate for MySQL
bind_dn_passwordNoBind DN Password for LDAP dynamic secrets
mongodb_passwordNoMongoDB server password
mongodb_usernameNoMongoDB server username
token_expirationNoToken expiration for LDAP dynamic secrets
delete_protectionNoProtection from accidental deletion [true/false]
external_usernameNoUse externally provided username [true/false]
mongodb_host_portNoMongoDB server host and port
rotation_intervalNoRotation interval in seconds (for rotated secrets)
secure_access_webNoEnable Web Secure Remote Access (for database dynamic secrets)
delete_immediatelyNoDelete immediately (bypass soft delete)
mongodb_server_uriNoMongoDB server URI
secure_access_hostNoTarget servers for connections
mongodb_custom_dataNoMongoDB custom data
mongodb_uri_optionsNoMongoDB server URI options
secure_access_delayNoDelay duration in seconds (0-120) after generating credentials
secure_access_enableNoEnable/Disable secure remote access [true/false]
db_server_certificatesNoDB server certificates for verification
mongodb_default_auth_dbNoMongoDB default authentication database
custom_username_templateNoCustom username template using go template syntax
fixed_user_claim_keynameNoKey-name of IdP claim for external usernameext_username
mongodb_atlas_project_idNoMongoDB Atlas project ID
mysql_creation_statementsNoMySQL creation statements
mysql_revocation_statementsNoMySQL revocation statements
mongodb_atlas_api_public_keyNoMongoDB Atlas API public key
producer_encryption_key_nameNoDynamic producer encryption key name
mongodb_atlas_api_private_keyNoMongoDB Atlas API private key
secure_access_certificate_issuerNoPath to SSH Certificate Issuer for Secure Access

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It offers minimal insight into side effects, permissions, reversibility, or safety risks (e.g., no warning that 'delete' might be permanent or require special privileges). The phrase 'smart detection' and 'securely retrieve' add some context, but the overall transparency is weak for a tool with such destructive operations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and largely redundant with the schema's action parameter description, which repeats the same action list verbatim. While the section headers (SUPPORTED ACTIONS, DELETE OPERATIONS) provide some structure, the content is not appropriately sized for the value it adds—many sentences simply restate what the schema already documents.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 76 parameters and 11 actions, the description provides a comprehensive action list and some delete examples, but it lacks per-action parameter mapping, prerequisites, or warnings. The output schema exists, so return values are covered, but the description does not fully compensate for the tool's complexity in navigating correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100% and the individual parameter descriptions are detailed, so the baseline is 3. The tool description adds a few usage examples (e.g., 'delete(name="/secret1")') and groups delete-related parameters, but it does not systematically explain which action requires which parameters or add meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create, retrieve, update, and delete secrets' and lists all supported actions, making the tool's purpose unambiguous. However, it does not explicitly differentiate this tool from sibling tools like manage_auth_methods or manage_targets, though the domain is evident from the name and content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through its 'SUPPORTED ACTIONS' list and delete examples, but it never explicitly states when to use this tool versus alternatives or provides exclusion criteria. It lacks a clear 'use this when...' statement, leaving the agent to infer context from the action names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sanyambassi/thales-cdsp-csm-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server