Skip to main content
Glama
Sign In
Infisical MCP Server

Infisical MCP Server

Official
by Infisical
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

update-secret

DestructiveIdempotent

Update an existing secret's value or name in a specified project and environment, optionally selecting its secret path.

Instructions

Update a secret in Infisical

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "environmentSlug": "<environmentSlug>",
      "secretName": "<secretName>"
    },
    "name": "update-secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe ID of the project to update the secret in (required)
secretNameYesThe current name of the secret to update (required)
secretPathNoThe path of the secret to update (Defaults to /)
secretValueNoThe new value of the secret to update (Optional)
newSecretNameNoThe new name of the secret to update (Optional)
environmentSlugYesThe slug of the environment to update the secret in (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

The description adds no behavioral detail beyond the word 'update'. The annotations already indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the description itself does not disclose side effects, overwrite behavior, or requirements. It neither enriches nor contradicts the annotations.

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

Conciseness5/5

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

The description is a single, compact sentence with no waste. The core action and object are front-loaded, so an agent can grasp the tool's purpose in under a second.

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

Completeness2/5

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

Given that this is a destructive, parameter-rich mutation with no output schema, the description is too thin. It should mention that the secret must already exist, that values/names are overwritten, and any preconditions around renaming or environment/path context.

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 coverage is 100%, and the description contributes no additional parameter-level insight. The baseline of 3 applies; the schema already explains what each parameter is for.

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 states a specific verb ('update') and a resource ('a secret in Infisical'). This clearly differentiates it from siblings like create-secret, delete-secret, and get-secret based on the operation alone.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus the other secret-related tools. It implies updating an existing secret, but it doesn't state prerequisites or when a user should choose this over create-secret or get-secret.

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

Deploy Server

Other Tools