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.

SERVERPortkey Admin SOURCEcodeswhat/portkey-admin-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about start_log_export

What does the start_log_export tool do? +

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.

How do I enforce a policy on start_log_export? +

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.

What risk level is start_log_export? +

start_log_export is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_log_export? +

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.

How do I block start_log_export completely? +

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.

What MCP server provides start_log_export? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Portkey Admin's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.