refresh_sdn_connector

A execute tool on the Fortimanager MCP server.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jmpijll-fortimanager-mcp/refresh-sdn-connector.md

WHAT IT DOES

What refresh_sdn_connector does on Fortimanager

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.

RISK

Why refresh_sdn_connector is rated High

The name suggests triggering a refresh/sync operation on an SDN connector, which is an external operation (Execute category). However, with no description available, confidence is low. Refreshing an SDN connector typically re-fetches dynamic address objects from cloud/SDN environments, which is a triggered external operation rather than a simple read or write.

From the tool's definition Tool name 'refresh_sdn_connector' — description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs refresh_sdn_connector 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_sdn_connector, this is the rule to start with:

refresh_sdn_connector Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_sdn_connector": {
      "limits": [
        {
          "counter": "refresh_sdn_connector_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every refresh_sdn_connector call is checked against it from then on.

FAQ

Questions about refresh_sdn_connector

What does the refresh_sdn_connector tool do? +

refresh_sdn_connector is a execute tool on the Fortimanager MCP server. 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.

How do I enforce a policy on refresh_sdn_connector? +

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.

What risk level is refresh_sdn_connector? +

refresh_sdn_connector is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit refresh_sdn_connector? +

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.

How do I block refresh_sdn_connector completely? +

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.

What MCP server provides refresh_sdn_connector? +

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.

KEEP EXPLORING

More on Fortimanager, and thousands of servers like it.

This server

All 584 Fortimanager tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →