run_intent_detection · Dialogflow CX MCP Server MCP

WHAT IT DOES

What run_intent_detection does on Dialogflow CX MCP Server

AI agents invoke run_intent_detection to trigger actions in Dialogflow CX MCP Server. 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 run_intent_detection needs a policy

run_intent_detection triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_intent_detection Rate-limited

run_intent_detection 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": {
    "run_intent_detection": {
      "limits": [
        {
          "counter": "run_intent_detection_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 Dialogflow CX MCP Server, so you can run agents against it safely.

FAQ

Questions about run_intent_detection

What does the run_intent_detection tool do? +

Run batch intent detection tests. It is categorised as a Execute tool in the Dialogflow CX MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_intent_detection? +

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

What risk level is run_intent_detection? +

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

Can I rate-limit run_intent_detection? +

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

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

run_intent_detection is provided by the Dialogflow CX MCP Server MCP server (yash-kavaiya/conversation_agents_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.