List secret names in the active project. Never returns values.
AI agents call list_secrets to retrieve information from Turbo Quant Memory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data (secret names/identifiers) without modifying, executing, or deleting anything. The tool explicitly guarantees it does not return secret values themselves, making it a safe information-retrieval operation. The low severity reflects that knowing secret names carries minimal risk compared to accessing secret values or performing destructive actions.
From the tool's definition Tool name: 'list_secrets'. Description: 'List secret names in the active project. Never returns values.' The explicit statement that it 'Never returns values' confirms this is a read-only operation that only enumerates metadata.
Documented attack patterns abuse exactly the kind of access list_secrets gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Turbo Quant Memory MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_secrets:
{
"version": "1",
"default": "deny",
"tools": {
"list_secrets": {}
}
}list_secrets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List secret names in the active project. Never returns values. It is categorised as a Read tool in the Turbo Quant Memory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Turbo Quant Memory MCP Server 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 Turbo Quant Memory MCP Server. 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 Turbo Quant Memory MCP Server MCP server (lexus2016/turbo_quant_memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Turbo Quant Memory MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 Turbo Quant Memory MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.