start_log_export · Portkey Admin MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

Parameter	Type	Required	Description
`export_id`	string	Yes	The unique ID of the log export to start

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why start_log_export needs a policy

start_log_export triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_log_export Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_log_export": {
      "limits": [
        {
          "counter": "start_log_export_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Portkey Admin, so you can run agents against it safely.

FAQ

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.

What parameters does start_log_export accept? +

start_log_export accepts 1 parameter: export_id. Required: export_id. The full parameter table on this page comes from the server's own tool schema.

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.