get_release_notes
Search for release notes and changelog information in the
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/get-release-notes.md
What get_release_notes does on Unofficial FortiMonitor MCP Server
AI agents call get_release_notes 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_release_notes is rated Low
This tool retrieves and searches historical release and changelog documentation. It does not modify, execute, delete, or commit financial transactions. The incomplete description ('in the...') suggests document retrieval, consistent with Read category. The blast radius of misuse is minimal—an agent could at worst retrieve unwanted documentation.
From the tool's definition Tool name 'get_release_notes' and description indicating it 'Search[es] for release notes and changelog information' clearly indicates a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_release_notes 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_release_notes, this is the rule to start with:
get_release_notes 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_release_notes call is checked against it from then on.
Questions about get_release_notes
Search for release notes and changelog information in the. 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_release_notes: 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_release_notes 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_release_notes 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_release_notes. 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_release_notes 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