cancel_log_export
Cancel a pending or running log export job, unlike start_log_export which queues one or delete_integration which removes the source. This permanently stops that export, takes effect immediately, and does not roll back already-processed rows; call create_log_export and start_log_export again to re...
This record as markdown: /tools/codeswhat-portkey-admin-mcp/cancel-log-export.md
What cancel_log_export does on Portkey Admin
AI agents call cancel_log_export to permanently remove resources in Portkey Admin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_log_export is rated Critical
Cancelling a log export job is an irreversible action: the job is permanently terminated with no rollback of partial state. To retry, the user must recreate and restart the entire export. This matches the Destructive category (irreversible action that cannot be undone). Severity is high because it can cause data loss or significant operational disruption if an export job is cancelled mid-flight.
From the tool's definition 'This permanently stops that export, takes effect immediately, and does not roll back already-processed rows' — the cancellation is irreversible and cannot be undone
Attacks that exploit this kind of access
The rule that runs cancel_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 cancel_log_export, this is the rule to start with:
cancel_log_export is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Portkey Admin, apply this rule, and every cancel_log_export call is checked against it from then on.
Questions about cancel_log_export
Cancel a pending or running log export job, unlike start_log_export which queues one or delete_integration which removes the source. This permanently stops that export, takes effect immediately, and does not roll back already-processed rows; call create_log_export and start_log_export again to retry. It is categorised as a Destructive tool in the Portkey Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for cancel_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.
cancel_log_export is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_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 cancel_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.
cancel_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