Skip to main content
Glama
sanyambassi

thales-cdsp-csm-mcp-server

by sanyambassi

manage_auth_methods

Create, list, update, and delete authentication methods with security controls like IP whitelisting, MFA, and access expiration for CipherTrust secrets management.

Instructions

AUTHENTICATION METHODS MANAGEMENT TOOL - Create, manage, and secure authentication methods

SUPPORTED ACTIONS: • create_api_key: Create API key authentication methods with IP restrictions and expiration • create_email: Create email-based authentication methods with MFA support • list: List all authentication methods with filtering and pagination • get: Retrieve detailed authentication method configuration and status • update: Modify authentication method properties, credentials, and settings • delete: Delete individual authentication methods with proper cleanup • delete_auth_methods: Bulk delete authentication methods within a specific path

SECURITY FEATURES: • IP address restrictions and CIDR whitelisting • Access expiration and JWT TTL management • Multi-factor authentication (MFA) support • Audit logging and compliance tracking • Delete protection and access control

Example: Create a secure API key for application authentication

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsonNoSet output format to JSON
nameNoAuthentication method name (required for create_api_key, update, delete, get)
pathNoPath for bulk operations (required for delete_auth_methods)
tagsNoList of tags attached to this object
typeNoAuth method types to filter by [api_key, azure_ad, oauth2/jwt, saml2, ldap, aws_iam, oidc, universal_identity, gcp, k8s, cert]
emailNoEmail address for email authentication method
actionYesAuthentication method management action to perform. SUPPORTED ACTIONS: 'create_api_key' (create API key authentication), 'create_email' (create email authentication), 'list' (list all authentication methods), 'get' (retrieve specific auth method details), 'update' (modify auth method properties), 'delete' (delete individual auth method), 'delete_auth_methods' (bulk delete auth methods by path)
filterNoFilter by auth method name or part of it
jwt_ttlNoJWT TTL
mfa_typeNoEnable two-factor-authentication via [email/auth app]email
new_nameNoNew name for the authentication method (for update action)
bound_ipsNoCIDR whitelist for IP restrictions
enable_mfaNoEnable MFA for this authentication method [True/False]
descriptionNoAuth Method description
gw_bound_ipsNoCIDR whitelist for Gateway IP restrictions
product_typeNoProduct type for auth method [sm, sra, pm, dp, ca]
accessibilityNoAccessibility levelregular
access_expiresNoAccess expiration date in Unix timestamp (0 for no expiry)
force_sub_claimsNoEnforce role-association must include sub claims
pagination_tokenNoNext page reference
audit_logs_claimsNoSubclaims to include in audit logs
delete_protectionNoProtection from accidental deletion [true/false]
expiration_event_inNoDays before expiration to be notified

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses destructive actions (delete, delete_auth_methods) and mentions delete protection, access control, and audit logging. However, it does not specify permission requirements or whether deletions are reversible, leaving some behavioral ambiguity.

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

Conciseness4/5

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

The description is well-structured with clear sections for supported actions and security features, and it is front-loaded with the tool's purpose. It is somewhat verbose but appropriate for a complex multi-action tool.

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

Completeness4/5

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

Given the tool's complexity (23 parameters, multiple actions) and the presence of an output schema, the description covers the main actions, security features, and an example. It lacks explicit prerequisites or error handling, but it is sufficient for most usage scenarios.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds context by mapping actions to the 'action' parameter and highlighting security-related parameters, but it does not explain each parameter in detail beyond the schema.

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

Purpose5/5

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

The description clearly states 'AUTHENTICATION METHODS MANAGEMENT TOOL - Create, manage, and secure authentication methods' and enumerates all supported actions (create_api_key, create_email, list, get, update, delete, delete_auth_methods), making purpose explicit and distinguishing it from sibling tools like manage_roles or manage_secrets.

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

Usage Guidelines4/5

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

The description provides clear context through SUPPORTED ACTIONS and SECURITY FEATURES, but it does not explicitly state when not to use this tool or name alternative tools. However, the tool's scope is well-defined, so an agent can infer when to use it.

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