list_secret_references
List Secret References without returning authentication configuration or resolved secret values. Filter by manager type, tags, or name and use a returned UUID or slug with get_secret_reference.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/list-secret-references.md
What list_secret_references does on Portkey Admin
AI agents call list_secret_references to retrieve information from Portkey Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_secret_references is rated Low
This is a query/list operation that retrieves information about secret references but explicitly does not return the actual secret values or authentication configurations. It has no side effects and is used only to discover or filter available secrets. This makes it a Read operation with low severity since it does not expose the sensitive data itself.
From the tool's definition Tool description explicitly states 'List Secret References' and 'without returning authentication configuration or resolved secret values', indicating it retrieves metadata only without exposing sensitive data.
Attacks that exploit this kind of access
The rule that runs list_secret_references safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_secret_references, this is the rule to start with:
list_secret_references is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Portkey Admin, apply this rule, and every list_secret_references call is checked against it from then on.
Questions about list_secret_references
List Secret References without returning authentication configuration or resolved secret values. Filter by manager type, tags, or name and use a returned UUID or slug with get_secret_reference. It is categorised as a Read tool in the Portkey Admin MCP Server, which means it retrieves data without modifying state.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for list_secret_references: 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 Portkey Admin. Nothing to install.
list_secret_references 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_secret_references 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_secret_references. 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_secret_references is provided by the Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Portkey Admin, and thousands of servers like it.
This server
Across the catalogue