Skip to main content
Glama
Sign In
Infisical MCP Server

Infisical MCP Server

Official
by Infisical
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list-secrets

Read-onlyIdempotent

List all secrets in a specified Infisical project and environment. Provide project ID and environment slug to retrieve secret names and values.

Instructions

List all secrets in a given Infisical project and environment

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>"
    },
    "name": "list-secrets"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe ID of the project to list the secrets from (required)
secretPathNoThe path of the secrets to list (Defaults to /)
includeImportsNoWhether to include secret imports (Defaults to true)
environmentSlugYesThe slug of the environment to list the secrets from (required)
expandSecretReferencesNoWhether to expand secret references (Defaults to true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds no behavioral context beyond the schema (e.g., no mention of pagination, default paths, or expansion behavior), but with annotations covering the key traits, a 3 is appropriate.

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 a single concise sentence that front-loads the action and resource. It is efficient and free of filler, though it could add a bit more scoping detail without becoming verbose.

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 read-only list operation with full schema coverage and safety annotations, the description is mostly adequate. However, it lacks context about return format, pagination, or how includeImports/expandSecretReferences affect results, which an agent might need to interpret the output correctly.

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 schema already documents all 5 parameters. The description adds no additional meaning beyond what the schema provides, so the baseline 3 applies.

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 states a clear verb ('List') and resource ('secrets') with scoping context ('in a given Infisical project and environment'). It distinguishes from mutation siblings like create-secret/delete-secret/update-secret, though it doesn't explicitly differentiate from get-secret (which is a sibling that also reads secrets).

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 for listing secrets in a project/environment, and the readOnlyHint annotation signals safe read-only usage. However, it does not explicitly state when to prefer this over get-secret or mention any exclusions or alternatives.

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