AI agents invoke wait_for_task_completion to trigger actions in Fortimanager. 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.
This tool appears to execute a wait/poll operation on FortiManager tasks. While not directly destructive or financial, it could trigger downstream actions or be used to coordinate the execution of other potentially harmful operations (e.g., waiting for a policy installation to complete before executing the next command in an attack sequence).
From the tool's definition Tool name 'wait_for_task_completion' indicates the tool awaits completion of a FortiManager task. In the context of a FortiManager JSON-RPC interface (as stated in server description), this likely monitors or blocks on an ongoing operation.
Documented attack patterns abuse exactly the kind of access wait_for_task_completion gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fortimanager, and nothing reaches the server without passing your rules. This is the rule we recommend for wait_for_task_completion:
{
"version": "1",
"default": "deny",
"tools": {
"wait_for_task_completion": {
"limits": [
{
"counter": "wait_for_task_completion_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}wait_for_task_completion 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.
Free to start. No card required.
wait_for_task_completion. It is categorised as a Execute tool in the Fortimanager MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fortimanager MCP server in PolicyLayer and add a rule for wait_for_task_completion: 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. Nothing to install.
wait_for_task_completion is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wait_for_task_completion 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.
Set action: deny in the PolicyLayer policy for wait_for_task_completion. 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.
wait_for_task_completion is provided by the Fortimanager MCP server (jmpijll/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
584 Fortimanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.