get_log_export
Fetch one log export job by export_id and return its status, filters, requested fields, and file metadata. Use this when you already know the target; use list_log_exports for a workspace-wide overview.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-log-export.md
What get_log_export does on Portkey Admin
AI agents call get_log_export 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_log_export is rated Low
This tool retrieves and queries information about a specific log export job. It performs no side effects, creates no data, executes no code, and makes no destructive changes. The verb 'Fetch' and the focus on returning metadata without altering state confirms this is a Read operation. Severity is low as misuse would only expose log export metadata, not cause system damage.
From the tool's definition Tool description explicitly states 'Fetch one log export job' and 'return its status, filters, requested fields, and file metadata' - all read-only retrieval operations with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs get_log_export 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_export, this is the rule to start with:
get_log_export 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_log_export call is checked against it from then on.
Questions about get_log_export
Fetch one log export job by export_id and return its status, filters, requested fields, and file metadata. Use this when you already know the target; use list_log_exports for a workspace-wide overview. 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_log_export: 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_log_export 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_log_export 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_log_export. 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_log_export 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