get_rotating_contact_active
Get the currently active (on-call) contact for a rotating contact schedule.
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/get-rotating-contact-active.md
What get_rotating_contact_active does on Unofficial FortiMonitor MCP Server
AI agents call get_rotating_contact_active to retrieve information from Unofficial FortiMonitor MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_rotating_contact_active is rated Low
This tool performs a simple data retrieval operation to fetch the current on-call contact from a rotating contact schedule. There are no side effects, no data modification, no destructive actions, and no financial implications. It is purely informational in nature, making it a Read operation with low severity—the impact of unauthorized access is limited to disclosure of on-call contact information.
From the tool's definition The tool name 'get_rotating_contact_active' and description 'Get the currently active (on-call) contact' indicate a retrieval operation that queries the status of a contact schedule without modifying any data.
Attacks that exploit this kind of access
The rule that runs get_rotating_contact_active 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 get_rotating_contact_active, this is the rule to start with:
get_rotating_contact_active is read-only, so it stays allowed. 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 get_rotating_contact_active call is checked against it from then on.
Questions about get_rotating_contact_active
Get the currently active (on-call) contact for a rotating contact schedule. It is categorised as a Read tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unofficial FortiMonitor MCP Server MCP server in PolicyLayer and add a rule for get_rotating_contact_active: 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.
get_rotating_contact_active is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_rotating_contact_active 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 get_rotating_contact_active. 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.
get_rotating_contact_active 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