enterprise_tool_execute · Serac MCP: Risk & Policy

WHAT IT DOES

What enterprise_tool_execute does on Serac

AI agents invoke enterprise_tool_execute to trigger actions in Serac. 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 enterprise_tool_execute needs a policy

This is a meta-execution tool that runs other enterprise tools dynamically by name. Because enterprise_tool_search discovers 400+ tools on a ServiceNow build agent, and the description does not restrict execution to read-only or safe operations, this tool can invoke any of those 400+ tools—many likely including Destructive (delete/drop), Financial, or Write operations.

From the tool's definition Tool description states 'Execute an enterprise tool by name' — direct execution of arbitrary enterprise tools with effects determined by tool arguments and parameters.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

enterprise_tool_execute Rate-limited

enterprise_tool_execute 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": {
    "enterprise_tool_execute": {
      "limits": [
        {
          "counter": "enterprise_tool_execute_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 Serac, so you can run agents against it safely.

FAQ

Questions about enterprise_tool_execute

What does the enterprise_tool_execute tool do? +

Execute an enterprise tool by name. Use enterprise_tool_search first to discover available tools. It is categorised as a Execute tool in the Serac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on enterprise_tool_execute? +

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

What risk level is enterprise_tool_execute? +

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

Can I rate-limit enterprise_tool_execute? +

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

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

enterprise_tool_execute is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.