execute_special_directive · Baby-SkyNet MCP: Risk & Policy

WHAT IT DOES

What execute_special_directive does on Baby-SkyNet

AI agents invoke execute_special_directive to trigger actions in Baby-SkyNet. 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 execute_special_directive needs a policy

Despite the opaque German description, the tool's name and context (in a memory management system with database and graph access) indicate it executes external system directives. This is Execute category because it triggers operations whose effects depend on the directive arguments.

From the tool's definition Tool name 'execute_special_directive' combined with description referencing 'proprietärer Systemanweisungen' (proprietary system directives) indicates execution of arbitrary system-level instructions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_special_directive Rate-limited

execute_special_directive 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": {
    "execute_special_directive": {
      "limits": [
        {
          "counter": "execute_special_directive_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 Baby-SkyNet, so you can run agents against it safely.

FAQ

Questions about execute_special_directive

What does the execute_special_directive tool do? +

🔐 Execute Special Directive - Verarbeitung proprietärer Systemanweisungen. It is categorised as a Execute tool in the Baby-SkyNet MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_special_directive? +

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

What risk level is execute_special_directive? +

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

Can I rate-limit execute_special_directive? +

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

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

execute_special_directive is provided by the Baby-SkyNet MCP server (spie-mkroehn/baby-skynet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.