get_secret_reference
Retrieve one Secret Reference by UUID or slug. Portkey masks sensitive authentication fields for non-system users; the tool returns metadata and the masked auth configuration, not the resolved external secret value.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-secret-reference.md
What get_secret_reference does on Portkey Admin
AI agents call get_secret_reference 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 get_secret_reference is rated Low
This is a retrieval operation with no side effects. Although it accesses secret metadata, the tool explicitly masks sensitive fields and does not return resolved secret values, minimizing exposure risk. Classification is Read with low severity since an attacker would gain only masked/metadata information, not usable credentials.
From the tool's definition Tool description explicitly states 'Retrieve one Secret Reference' and 'returns metadata and the masked auth configuration' — characteristic Read operations.
Attacks that exploit this kind of access
The rule that runs get_secret_reference 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 get_secret_reference, this is the rule to start with:
get_secret_reference 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 get_secret_reference call is checked against it from then on.
Questions about get_secret_reference
Retrieve one Secret Reference by UUID or slug. Portkey masks sensitive authentication fields for non-system users; the tool returns metadata and the masked auth configuration, not the resolved external secret value. 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 get_secret_reference: 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.
get_secret_reference 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 get_secret_reference 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 get_secret_reference. 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.
get_secret_reference 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