sac_import_run_job

THE RISK

High Risk

Why sac_import_run_job needs a policy

This tool executes an import job in SAP Analytics Cloud. Executing an import job triggers an external operation that loads data into the system, which can have significant side effects such as overwriting existing data, modifying datasets, or altering system state. While it may involve writing data, the primary action is executing/triggering a job process.

From the tool's definition 'Execute validated import job' — the tool runs/triggers an import job operation

Documented attack patterns abuse exactly the kind of access sac_import_run_job gives an agent:

POLICY

How to control sac_import_run_job

PolicyLayer is an MCP gateway — it sits between your AI agents and Sap Analytics Cloud, and nothing reaches the server without passing your rules. This is the rule we recommend for sac_import_run_job:

policy.json

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

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

Create a free account and register Sap Analytics Cloud — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sap Analytics Cloud tools

Destructive sac_stories_delete Delete a story. Destructive sac_transport_delete_content Delete a content item. Destructive sac_users_bulk Bulk SCIM operations (create/update/delete multiple users/groups). Destructive sac_users_delete Delete a user. Destructive sac_export_delete_subscription Delete data export subscription(s). Destructive sac_import_delete_job Delete an import job. Destructive sac_schedule_delete Delete a publication schedule. Execute sac_multi_action_execute Execute a multi action. ID format: <packageId>:<objectId>. Body requires parameterValues a

All 90 Sap Analytics Cloud tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Sap Analytics Cloud → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sac_import_run_job

What does the sac_import_run_job tool do? +

Execute validated import job. It is categorised as a Execute tool in the Sap Analytics Cloud MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sac_import_run_job? +

Register the Sap Analytics Cloud MCP server in PolicyLayer and add a rule for sac_import_run_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 Sap Analytics Cloud. Nothing to install.

What risk level is sac_import_run_job? +

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

Can I rate-limit sac_import_run_job? +

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

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

sac_import_run_job is provided by the Sap Analytics Cloud MCP server (jumenengels/sap_analytics_cloud_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sap Analytics Cloud tool call.

Start from Sap Analytics Cloud, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →