Retry a failed, canceled, or otherwise terminal import job.
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.
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
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.
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.
retry_import_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →