flee · Integration Quest MCP: Risk & Policy

WHAT IT DOES

What flee does on Integration Quest

AI agents invoke flee to trigger actions in Integration Quest. 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 flee needs a policy

This tool triggers a game action (fleeing from combat) whose outcome depends on character stats. It modifies game state (exits combat encounter) based on runtime conditions. It's not a simple read, but it's also not destructive or financial — it executes a game mechanic within the RPG simulation.

From the tool's definition Attempt graceful degradation (escape combat). Success based on Rate Agility.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

flee Rate-limited

flee 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": {
    "flee": {
      "limits": [
        {
          "counter": "flee_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 Integration Quest, so you can run agents against it safely.

FAQ

Questions about flee

What does the flee tool do? +

Attempt graceful degradation (escape combat). Success based on Rate Agility. It is categorised as a Execute tool in the Integration Quest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on flee? +

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

What risk level is flee? +

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

Can I rate-limit flee? +

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

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

flee is provided by the Integration Quest MCP server (mattcarpenter-workato/workato-integration-quest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.