sentinel_script_run · SentinelX Core MCP: Risk & Policy

WHAT IT DOES

What sentinel_script_run does on SentinelX Core MCP

AI agents invoke sentinel_script_run to trigger actions in SentinelX Core MCP. 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 sentinel_script_run needs a policy

This tool executes scripts, which is an Execute category action. The 'temporary structured script' execution through a dedicated endpoint could have side effects depending on script content. Given the broader server context (SentinelX Core HTTP agent with authentication), script execution poses significant risk if an AI agent runs malicious or unintended scripts.

From the tool's definition Tool name contains 'run' and description states 'Execute a temporary structured script through SentinelX (/script/run)'. The verb 'Execute' directly indicates code execution capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sentinel_script_run Rate-limited

sentinel_script_run 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": {
    "sentinel_script_run": {
      "limits": [
        {
          "counter": "sentinel_script_run_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 SentinelX Core MCP, so you can run agents against it safely.

FAQ

Questions about sentinel_script_run

What does the sentinel_script_run tool do? +

Execute a temporary structured script through SentinelX (/script/run). It is categorised as a Execute tool in the SentinelX Core MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sentinel_script_run? +

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

What risk level is sentinel_script_run? +

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

Can I rate-limit sentinel_script_run? +

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

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

sentinel_script_run is provided by the SentinelX Core MCP server (pensados/sentinelx-core-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.