Low Risk

get_backup_settings

get_backup_settings

How to control get_backup_settings ↓

What get_backup_settings does on Fortimanager

AI agents call get_backup_settings 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_backup_settings needs a policy

The tool name strongly suggests querying or retrieving backup settings rather than creating, modifying, or deleting them. This aligns with the Read category (retrieves or queries data; no side effects). While the empty description reduces confidence slightly, the verb 'get' combined with 'settings' as a configuration query is a reliable indicator of read-only behavior with minimal blast radius if misused.

From the tool's definition Tool name 'get_backup_settings' indicates retrieval of backup configuration settings with no modification. Description is empty, limiting specificity.

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

How to control get_backup_settings

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

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

get_backup_settings 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_backup_settings

What does the get_backup_settings tool do? +

get_backup_settings. 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_backup_settings? +

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

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

Can I rate-limit get_backup_settings? +

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

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

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