retry_export_job · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What retry_export_job does on Sanka MCP Server

AI agents invoke retry_export_job to trigger actions in Sanka MCP Server. 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 IT NEEDS A POLICY

Why retry_export_job needs a policy

Retrying an export job triggers an external operation to re-execute a previously failed process. It doesn't simply read data, nor does it irreversibly delete anything — it initiates execution of a job pipeline again, making Execute the most appropriate category. Misuse could cause unintended repeated data exports or resource consumption, warranting medium severity.

From the tool's definition Retry a failed, canceled, or otherwise terminal export job

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

retry_export_job Rate-limited

retry_export_job 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": {
    "retry_export_job": {
      "limits": [
        {
          "counter": "retry_export_job_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 Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about retry_export_job

What does the retry_export_job tool do? +

Retry a failed, canceled, or otherwise terminal export job. It is categorised as a Execute tool in the Sanka MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on retry_export_job? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for retry_export_job: 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 Sanka MCP Server. Nothing to install.

What risk level is retry_export_job? +

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

Can I rate-limit retry_export_job? +

Yes. Add a rate_limit block to the retry_export_job 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 retry_export_job completely? +

Set action: deny in the PolicyLayer policy for retry_export_job. 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 retry_export_job? +

retry_export_job is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.