get_log

Get one gateway request log by ID, including its request, response, usage, cost, and metadata payload when available. For path_format v2, also provide the log

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-log.md

WHAT IT DOES

What get_log does on Portkey Admin

AI agents call get_log 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_log is rated Low

Tool retrieves existing log data without modification or side effects. No creation, deletion, or code execution involved.

From the tool's definition Get one gateway request log by ID, including its request, response, usage, cost, and metadata payload.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_log 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_log, this is the rule to start with:

get_log Allowed

get_log 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_log": {}
  }
}

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_log call is checked against it from then on.

FAQ

Questions about get_log

What does the get_log tool do? +

Get one gateway request log by ID, including its request, response, usage, cost, and metadata payload when available. For path_format v2, also provide the log. 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_log? +

Register the Portkey Admin MCP server in PolicyLayer and add a rule for get_log: 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_log? +

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

Can I rate-limit get_log? +

Yes. Add a rate_limit block to the get_log 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_log completely? +

Set action: deny in the PolicyLayer policy for get_log. 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_log? +

get_log 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 170 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 →