get_script_log_summary

Get script execution log summary.

SERVERFortiManager MCP Server SOURCErstierli/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/rstierli-fortimanager-mcp/get-script-log-summary.md

WHAT IT DOES

What get_script_log_summary does on FortiManager MCP Server

AI agents call get_script_log_summary to retrieve information from FortiManager MCP Server 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_script_log_summary is rated Low

This tool retrieves and queries existing log summary data from FortiManager. It is a passive read operation that does not create, modify, delete, or execute any code or commands. No side effects are expected from retrieving logs.

From the tool's definition Tool name 'get_script_log_summary' and description 'Get script execution log summary' indicate retrieval of historical log data with no modification, deletion, or execution of scripts.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_script_log_summary safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FortiManager MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_script_log_summary, this is the rule to start with:

get_script_log_summary Allowed

get_script_log_summary 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_script_log_summary": {}
  }
}

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

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

FAQ

Questions about get_script_log_summary

What does the get_script_log_summary tool do? +

Get script execution log summary. It is categorised as a Read tool in the FortiManager MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_script_log_summary? +

Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for get_script_log_summary: 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 MCP Server. Nothing to install.

What risk level is get_script_log_summary? +

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

Can I rate-limit get_script_log_summary? +

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

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

get_script_log_summary is provided by the FortiManager MCP Server MCP server (rstierli/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 MCP Server, and thousands of servers like it.

This server

All 236 FortiManager MCP Server 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 →