get_onsight_countermeasures
Get countermeasure metadata for a specific OnSight instance.
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/get-onsight-countermeasures.md
What get_onsight_countermeasures does on Unofficial FortiMonitor MCP Server
AI agents call get_onsight_countermeasures 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_onsight_countermeasures is rated Low
This tool retrieves metadata about countermeasures from an OnSight instance. The use of 'get' combined with 'metadata' indicates a read-only query operation that does not modify, execute, delete, or commit any financial actions. The blast radius of misuse is minimal—exposure of monitoring metadata would be a confidentiality concern but does not enable unauthorized changes or resource depletion.
From the tool's definition Tool name 'get_onsight_countermeasures' and description 'Get countermeasure metadata for a specific OnSight instance' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_onsight_countermeasures 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_onsight_countermeasures, this is the rule to start with:
get_onsight_countermeasures 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_onsight_countermeasures call is checked against it from then on.
Questions about get_onsight_countermeasures
Get countermeasure metadata for a specific OnSight instance. 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_onsight_countermeasures: 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_onsight_countermeasures 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_onsight_countermeasures 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_onsight_countermeasures. 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_onsight_countermeasures 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