get_api_key
Fetch one API key by UUID without revealing the secret. Use this to inspect scopes, defaults, limits, expiration, and reset state before changing access.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-api-key.md
What get_api_key does on Portkey Admin
AI agents call get_api_key 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_api_key is rated Low
This is a Read operation as it retrieves and inspects API key metadata (scopes, defaults, limits, expiration, reset state) without modifying data. Severity is medium because while it doesn't directly expose secrets, API key metadata could be used to understand access patterns or inform targeted attacks, and reading API key information is sensitive in administrative contexts.
From the tool's definition Tool description states 'Fetch one API key by UUID without revealing the secret' - a retrieval operation. However, API keys are security-sensitive credentials and examining them could inform privilege escalation attacks.
Attacks that exploit this kind of access
The rule that runs get_api_key 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_api_key, this is the rule to start with:
get_api_key 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_api_key call is checked against it from then on.
Questions about get_api_key
Fetch one API key by UUID without revealing the secret. Use this to inspect scopes, defaults, limits, expiration, and reset state before changing access. 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_api_key: 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_api_key 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_api_key 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_api_key. 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_api_key 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