enter_diagnostic_code · Integration Quest MCP: Risk & Policy

WHAT IT DOES

What enter_diagnostic_code does on Integration Quest

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

Although this is part of an RPG game server, the tool explicitly runs system diagnostics (not simulated game actions like the sibling tools examine, explore, attack). Running diagnostics is an Execute category operation because it triggers external system operations whose effects depend on the diagnostic code argument.

From the tool's definition Tool performs 'Run system diagnostics with a diagnostic code' - actively executes diagnostic operations in a live system based on user-supplied input (the diagnostic code argument).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

enter_diagnostic_code Rate-limited

enter_diagnostic_code 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": {
    "enter_diagnostic_code": {
      "limits": [
        {
          "counter": "enter_diagnostic_code_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 enter_diagnostic_code

What does the enter_diagnostic_code tool do? +

Run system diagnostics with a diagnostic code. 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 enter_diagnostic_code? +

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

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

Can I rate-limit enter_diagnostic_code? +

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

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

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