rename_device

A write tool on the Fortimanager MCP server.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jmpijll-fortimanager-mcp/rename-device.md

WHAT IT DOES

What rename_device does on Fortimanager

AI agents use rename_device to create or update resources in Fortimanager, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fortimanager environment.

RISK

Why rename_device is rated Medium

Renaming a device is a reversible write operation that modifies configuration metadata. It does not delete data (not Destructive), does not involve financial transactions (not Financial), and does not execute arbitrary code (not Execute). While potentially impactful in a managed network environment, the blast radius is limited to metadata changes.

From the tool's definition Tool name 'rename_device' indicates modification of device properties. No description provided; classification based on naming convention and context of sibling management tools on FortiManager MCP server.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

rename_device Rate-limited

rename_device stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_device": {
      "limits": [
        {
          "counter": "rename_device_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about rename_device

What does the rename_device tool do? +

rename_device is a write tool on the Fortimanager MCP server. It is categorised as a Write tool in the Fortimanager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_device? +

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

rename_device is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_device? +

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

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

rename_device 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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →