compile_objectscript_package · Iris Execute MCP

WHAT IT DOES

What compile_objectscript_package does on Iris Execute

AI agents invoke compile_objectscript_package to trigger actions in Iris Execute. 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 compile_objectscript_package needs a policy

Code compilation is an Execute operation—it triggers external processes and can have side effects beyond simple data retrieval. While not inherently destructive, it runs code whose behavior depends on the package argument and the code being compiled. The blast radius is high because malicious package compilation could inject code, alter system behavior, or cause cascading failures.

From the tool's definition Tool is part of an 'ObjectScript execution' server and named 'compile_objectscript_package', which compiles code. Sibling tools include 'execute_classmethod' and 'execute_command' indicating this server is built for code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

compile_objectscript_package Rate-limited

compile_objectscript_package 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": {
    "compile_objectscript_package": {
      "limits": [
        {
          "counter": "compile_objectscript_package_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 Iris Execute, so you can run agents against it safely.

FAQ

Questions about compile_objectscript_package

What does the compile_objectscript_package tool do? +

compile_objectscript_package. It is categorised as a Execute tool in the Iris Execute MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on compile_objectscript_package? +

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

What risk level is compile_objectscript_package? +

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

Can I rate-limit compile_objectscript_package? +

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

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

compile_objectscript_package is provided by the Iris Execute MCP server (jbrandtmse/iris-execute-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.