get_log_settings

A read tool on the Fortimanager MCP server.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jmpijll-fortimanager-mcp/get-log-settings.md

WHAT IT DOES

What get_log_settings does on Fortimanager

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

RISK

Why get_log_settings is rated Low

The 'get_' prefix is a strong signal of read-only retrieval behavior. Log settings queries retrieve system configuration without side effects. Empty descriptions lower confidence slightly, but naming convention is clear enough to categorize as Read with high confidence. Severity is low because reading settings poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'get_log_settings' uses the 'get' verb, indicating data retrieval. Description is empty, but the name itself strongly suggests querying configuration settings rather than modifying or executing operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_log_settings Allowed

get_log_settings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_log_settings": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_log_settings

What does the get_log_settings tool do? +

get_log_settings is a read tool on the Fortimanager MCP server. 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_log_settings? +

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

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

Can I rate-limit get_log_settings? +

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

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

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

KEEP EXPLORING

More on Fortimanager, and thousands of servers like it.

This server

All 584 Fortimanager tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →