move · Integration Quest MCP: Risk & Policy

WHAT IT DOES

What move does on Integration Quest

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

The tool triggers a state-change action within the RPG (moving the character to a different location/system), which is an operation with side effects on game state. It is not purely reading data, and 'navigate to an adjacent system' implies executing a transition. Severity is low since this is confined to an in-game RPG context with no real-world impact.

From the tool's definition Navigate to an adjacent system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move Rate-limited

move 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": {
    "move": {
      "limits": [
        {
          "counter": "move_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 move

What does the move tool do? +

Navigate to an adjacent system. 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 move? +

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

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

Can I rate-limit move? +

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

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

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

// THE FULL RECORD

move is one line of Integration Quest's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →