execute_classmethod · Iris Execute MCP: Risk & Policy

WHAT IT DOES

What execute_classmethod does on Iris Execute

AI agents invoke execute_classmethod 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 execute_classmethod needs a policy

This tool executes ObjectScript class methods, which is code execution whose effects depend on which method is invoked and its arguments. This could trigger side effects, data modifications, or external operations. While not inherently destructive or financial, execution of untrusted or poorly-specified methods poses significant risk.

From the tool's definition Tool name 'execute_classmethod' on a server described as providing 'ObjectScript execution' capabilities. Sibling tools include 'execute_command' and 'execute_unit_tests', confirming this server's focus on code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_classmethod Rate-limited

execute_classmethod 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_classmethod": {
      "limits": [
        {
          "counter": "execute_classmethod_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 execute_classmethod

What does the execute_classmethod tool do? +

execute_classmethod. 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 execute_classmethod? +

Register the Iris Execute MCP server in PolicyLayer and add a rule for execute_classmethod: 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 execute_classmethod? +

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

Can I rate-limit execute_classmethod? +

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

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

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