Low Risk

get_cloud_connector_services

get_cloud_connector_services

How to control get_cloud_connector_services ↓

What get_cloud_connector_services does on Fortimanager

AI agents call get_cloud_connector_services to retrieve information from Fortimanager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_cloud_connector_services needs a policy

The 'get_' prefix strongly indicates this tool retrieves cloud connector service information without modifying state. However, with an empty description and given the infrastructure management context of this MCP server, there is some uncertainty about what 'cloud connector services' exposes—it could potentially retrieve sensitive configuration or credentials.

From the tool's definition Tool name 'get_cloud_connector_services' follows a 'get_*' pattern indicating data retrieval. The description is empty, limiting certainty.

Documented attack patterns abuse exactly the kind of access get_cloud_connector_services gives an agent:

How to control get_cloud_connector_services

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 get_cloud_connector_services:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cloud_connector_services": {}
  }
}

get_cloud_connector_services is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Fortimanager — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_cloud_connector_services

What does the get_cloud_connector_services tool do? +

get_cloud_connector_services. It is categorised as a Read tool in the Fortimanager MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cloud_connector_services? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for get_cloud_connector_services: 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 get_cloud_connector_services? +

get_cloud_connector_services is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_cloud_connector_services? +

Yes. Add a rate_limit block to the get_cloud_connector_services 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 get_cloud_connector_services completely? +

Set action: deny in the PolicyLayer policy for get_cloud_connector_services. 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 get_cloud_connector_services? +

get_cloud_connector_services 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.

Enforce policy on every Fortimanager tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.