compile · McFlow MCP: Risk & Policy

WHAT IT DOES

What compile does on McFlow

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

The 'compile' action with code/prompt injection capability is an Execute risk because it runs or processes external code within the workflow context. While not Destructive (no irreversible deletion), it goes beyond Write (mere modification) by actively executing code whose behavior depends on the injected content.

From the tool's definition Tool description states 'Compile all workflows by injecting external code/prompt files' — this involves executing code (injected code/prompts) into workflows, which triggers external operations whose effects depend on what code is injected.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

compile Rate-limited

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

FAQ

Questions about compile

What does the compile tool do? +

Compile all workflows by injecting external code/prompt files. It is categorised as a Execute tool in the McFlow 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? +

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

What risk level is compile? +

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

Can I rate-limit compile? +

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

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

compile is provided by the McFlow MCP server (mckinleymedia/mcflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.