List secret keys
AI agents call secrets.list to retrieve information from MCP Fullstack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although this is a Read operation (no data modification), the severity is high because accessing secret keys could expose authentication credentials, API keys, or other sensitive materials that enable further attacks. The blast radius is significant if an AI agent obtains and exfiltrates secrets, even though the tool itself performs only retrieval.
From the tool's definition Tool name 'secrets.list' and description 'List secret keys' indicate this retrieves sensitive credential data without modification or deletion.
Attacks that exploit this kind of access
List secret keys. It is categorised as a Read tool in the MCP Fullstack MCP Server, which means it retrieves data without modifying state.
Register the MCP Fullstack MCP server in PolicyLayer and add a rule for secrets.list: 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 MCP Fullstack. Nothing to install.
secrets.list 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 secrets.list 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 secrets.list. 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.
secrets.list is provided by the MCP Fullstack MCP server (jacobfv/mcp-fullstack). 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 →