refresh_external_threat_feed
Manually refresh an external threat feed.
This record as markdown: /tools/jmpijll-fortimanager-mcp/refresh-external-threat-feed.md
What refresh_external_threat_feed does on Fortimanager
AI agents invoke refresh_external_threat_feed 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.
Why refresh_external_threat_feed is rated High
This tool triggers an external operation — forcing an update/pull of threat feed data from an external source. It's not a simple read (it causes a side effect: fetching and updating threat intelligence data), not a write (it doesn't create/modify user-defined data), and not destructive. It executes an action (refresh/sync) that interacts with external systems, making Execute the most appropriate category.
From the tool's definition Manually refresh an external threat feed
Attacks that exploit this kind of access
The rule that runs refresh_external_threat_feed safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fortimanager, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For refresh_external_threat_feed, this is the rule to start with:
refresh_external_threat_feed 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 Fortimanager, apply this rule, and every refresh_external_threat_feed call is checked against it from then on.
Questions about refresh_external_threat_feed
Manually refresh an external threat feed. 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 refresh_external_threat_feed: 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.
refresh_external_threat_feed 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 refresh_external_threat_feed 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 refresh_external_threat_feed. 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.
refresh_external_threat_feed 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.
More on Fortimanager, and thousands of servers like it.
Across the catalogue