retry_import_job

Retry a failed, canceled, or otherwise terminal import job.

SERVERSanka MCP Server SOURCEsankahq/sanka-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/sankahq-sanka-mcp/retry-import-job.md

WHAT IT DOES

What retry_import_job does on Sanka MCP Server

AI agents invoke retry_import_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.

RISK

Why retry_import_job is rated High

This tool re-triggers an import job execution. It causes an external operation to run again (importing data), which classifies it as Execute. The blast radius is medium — misuse could cause duplicate or unintended data imports, but it is not inherently destructive or financial in nature.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs retry_import_job safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For retry_import_job, this is the rule to start with:

retry_import_job Rate-limited

retry_import_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_import_job": {
      "limits": [
        {
          "counter": "retry_import_job_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every retry_import_job call is checked against it from then on.

FAQ

Questions about retry_import_job

What does the retry_import_job tool do? +

Retry a failed, canceled, or otherwise terminal import 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_import_job? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for retry_import_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_import_job? +

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

Can I rate-limit retry_import_job? +

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

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

retry_import_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.

KEEP EXPLORING

More on Sanka MCP Server, and thousands of servers like it.

This server

All 349 Sanka MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →