defend · Integration Quest MCP: Risk & Policy

WHAT IT DOES

What defend does on Integration Quest

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

The tool executes a game action (defensive stance) that modifies combat state and triggers in-game retry logic. It has real side effects within the game engine but is limited to RPG game state with no external data or financial impact. 'Triggers retry logic' suggests it executes internal game mechanics.

From the tool's definition 'Defensive stance. Reduces incoming damage by 50% and triggers retry logic if equipped.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

defend Rate-limited

defend 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": {
    "defend": {
      "limits": [
        {
          "counter": "defend_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 defend

What does the defend tool do? +

Defensive stance. Reduces incoming damage by 50% and triggers retry logic if equipped. 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 defend? +

Register the Integration Quest MCP server in PolicyLayer and add a rule for defend: 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 defend? +

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

Can I rate-limit defend? +

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

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

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