start_log_export
Start processing a previously created log export job. This is asynchronous, only queues the export, and does not return rows or a download file; use get_log_export to poll progress and download_log_export after the job completes.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/start-log-export.md
What start_log_export does on Portkey Admin
AI agents invoke start_log_export to trigger actions in Portkey Admin. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why start_log_export is rated High
This tool initiates a background job that processes log data. While not destructive (the export doesn't modify or delete the underlying logs), it executes an operation on infrastructure that has external effects (job queueing, resource consumption, and subsequent data retrieval).
From the tool's definition The tool description states it 'Start[s] processing a previously created log export job' and 'queues the export', indicating it triggers an external asynchronous operation whose execution depends on the prior state and the export job parameters.
Attacks that exploit this kind of access
The rule that runs start_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 start_log_export, this is the rule to start with:
start_log_export stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 start_log_export call is checked against it from then on.
Questions about start_log_export
Start processing a previously created log export job. This is asynchronous, only queues the export, and does not return rows or a download file; use get_log_export to poll progress and download_log_export after the job completes. It is categorised as a Execute tool in the Portkey Admin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for start_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.
start_log_export is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_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 start_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.
start_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.
Across the catalogue