List static secrets in an Infisical project environment.
AI agents call list_secrets to retrieve information from Infisical MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and lists secrets without creating, modifying, or deleting them. This is a Read operation. Severity is medium rather than low because secrets are sensitive credentials; unauthorized listing could expose authentication tokens, API keys, or other confidential data, creating a reputational or operational risk if misused by a compromised agent. However, it has no direct destructive capability.
From the tool's definition Tool name 'list_secrets' and description 'List static secrets in an Infisical project environment' indicates retrieval/querying of secret data without modification.
Attacks that exploit this kind of access
List static secrets in an Infisical project environment. It is categorised as a Read tool in the Infisical MCP MCP Server, which means it retrieves data without modifying state.
Register the Infisical MCP server in PolicyLayer and add a rule for list_secrets: 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 Infisical MCP. Nothing to install.
list_secrets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_secrets 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.
Set action: deny in the PolicyLayer policy for list_secrets. 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.
list_secrets is provided by the Infisical MCP server (plgonzalezrx8/infisicalmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →