continue_guided_session
Continue an active guided session by providing the user
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/continue-guided-session.md
What continue_guided_session does on Unofficial FortiMonitor MCP Server
AI agents invoke continue_guided_session to trigger actions in Unofficial FortiMonitor 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 continue_guided_session is rated High
The tool appears to continue an active guided session, which implies triggering or advancing an ongoing interactive operation. This is most consistent with Execute. However, the description is truncated and provides insufficient detail to determine the exact action. Confidence is lowered accordingly.
From the tool's definition 'Continue an active guided session by providing the user' — description is truncated/uninformative
Attacks that exploit this kind of access
The rule that runs continue_guided_session safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unofficial FortiMonitor MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For continue_guided_session, this is the rule to start with:
continue_guided_session 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unofficial FortiMonitor MCP Server, apply this rule, and every continue_guided_session call is checked against it from then on.
Questions about continue_guided_session
Continue an active guided session by providing the user. It is categorised as a Execute tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unofficial FortiMonitor MCP Server MCP server in PolicyLayer and add a rule for continue_guided_session: 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 Unofficial FortiMonitor MCP Server. Nothing to install.
continue_guided_session 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 continue_guided_session 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 continue_guided_session. 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.
continue_guided_session is provided by the Unofficial FortiMonitor MCP Server MCP server (gjenkins20/unofficial-fortimonitor-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unofficial FortiMonitor MCP Server, and thousands of servers like it.
Across the catalogue