wait_for_task · FortiManager MCP Server MCP: Risk & Policy

WHAT IT DOES

What wait_for_task does on FortiManager MCP Server

AI agents invoke wait_for_task to trigger actions in FortiManager 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 wait_for_task needs a policy

Without a description, confidence is reduced. However, the pattern of task-wait behavior in infrastructure management APIs typically constitutes Execute rather than Read, since it controls execution flow and timing of dependent operations. The blast radius is medium—misuse could cause an agent to hang or proceed prematurely with incomplete configurations, but does not directly delete, modify, or move resources.

From the tool's definition Tool name 'wait_for_task' with empty description suggests it monitors or polls the status of asynchronous operations on FortiManager.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait_for_task Rate-limited

wait_for_task 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": {
    "wait_for_task": {
      "limits": [
        {
          "counter": "wait_for_task_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 FortiManager MCP Server, so you can run agents against it safely.

FAQ

Questions about wait_for_task

What does the wait_for_task tool do? +

wait_for_task. It is categorised as a Execute tool in the FortiManager 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 wait_for_task? +

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

What risk level is wait_for_task? +

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

Can I rate-limit wait_for_task? +

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

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

wait_for_task is provided by the FortiManager MCP Server MCP server (rstierli/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.