get_secret_reference

SERVERPortkey Admin SOURCEcodeswhat/portkey-admin-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-secret-reference.md

WHAT IT DOES

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.

RISK

Why get_secret_reference is rated Low

Even though get_secret_reference only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

get_secret_reference is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_secret_reference": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about get_secret_reference

What does the get_secret_reference tool do? +

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.

How do I enforce a policy on get_secret_reference? +

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.

What risk level is get_secret_reference? +

get_secret_reference is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_secret_reference? +

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.

How do I block get_secret_reference completely? +

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.

What MCP server provides get_secret_reference? +

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.

KEEP EXPLORING

More on Portkey Admin, and thousands of servers like it.

This server

All 156 Portkey Admin tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →