list_recent_tasks

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/list-recent-tasks.md

WHAT IT DOES

What list_recent_tasks does on Fortimanager

AI agents call list_recent_tasks 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 list_recent_tasks is rated Low

The tool name strongly suggests querying or retrieving a list of recent tasks from FortiManager, which is a non-destructive read operation. Despite the empty description, the naming convention ('list_*') is a reliable indicator of Read-category behavior. Low severity because listing tasks provides information only, with minimal blast radius if misused.

From the tool's definition Tool name 'list_recent_tasks' indicates retrieval of task history with no modification; verb 'list' is a classic Read operation. Description is empty, which reduces confidence slightly.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_recent_tasks Allowed

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

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 list_recent_tasks call is checked against it from then on.

FAQ

Questions about list_recent_tasks

What does the list_recent_tasks tool do? +

list_recent_tasks 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 list_recent_tasks? +

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

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

Can I rate-limit list_recent_tasks? +

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

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

list_recent_tasks 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

list_tasks on 0rca Dojo MCP Server →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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