AI agents invoke refresh_sdn_connector 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.
An SDN (Software-Defined Networking) connector refresh typically triggers an external operation to re-synchronize network data from a cloud or SDN provider. This falls under Execute as it initiates an external operation. However, the empty description significantly reduces confidence. Severity is medium given potential impact on network configuration synchronization.
From the tool's definition Tool name 'refresh_sdn_connector' suggests triggering a refresh/sync operation on an SDN connector; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access refresh_sdn_connector gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fortimanager, and nothing reaches the server without passing your rules. This is the rule we recommend for refresh_sdn_connector:
{
"version": "1",
"default": "deny",
"tools": {
"refresh_sdn_connector": {
"limits": [
{
"counter": "refresh_sdn_connector_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}refresh_sdn_connector 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.
Free to start. No card required.
refresh_sdn_connector. 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_sdn_connector: 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_sdn_connector 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_sdn_connector 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_sdn_connector. 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_sdn_connector 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.
Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
584 Fortimanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.