replace_security_profile_entries
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/replace-security-profile-entries.md
What replace_security_profile_entries does on Fortimanager
AI agents use replace_security_profile_entries 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.
Why replace_security_profile_entries is rated Medium
The tool modifies security profile data (reversible via subsequent writes) but does not permanently delete or execute arbitrary code. Replacing security profiles affects network security policy and could be misused to weaken protections, but the operation is reversible. Classified as Write rather than Execute because it modifies a data structure rather than triggering external operations.
From the tool's definition Tool name 'replace_security_profile_entries' indicates modification of security profile configurations in FortiManager. The verb 'replace' denotes overwriting existing entries.
Attacks that exploit this kind of access
The rule that runs replace_security_profile_entries 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 replace_security_profile_entries, this is the rule to start with:
replace_security_profile_entries 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every replace_security_profile_entries call is checked against it from then on.
Questions about replace_security_profile_entries
replace_security_profile_entries 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.
Register the Fortimanager MCP server in PolicyLayer and add a rule for replace_security_profile_entries: 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.
replace_security_profile_entries is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the replace_security_profile_entries 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.
Set action: deny in the PolicyLayer policy for replace_security_profile_entries. 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.
replace_security_profile_entries 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.
More on Fortimanager, and thousands of servers like it.
This server
Across the catalogue