AI agents use set_object_meta_field 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.
The 'set_' prefix strongly indicates a write/modification operation. Given the FortiManager context (network security appliance management), modifying object metadata could affect policy application or system behavior, but is reversible and less severe than directly deleting policies or executing commands. Medium severity due to potential for configuration drift or unintended side effects.
From the tool's definition Tool name 'set_object_meta_field' indicates modification of metadata fields on objects within FortiManager; no description provided but naming pattern suggests write operations on configuration/policy objects.
Documented attack patterns abuse exactly the kind of access set_object_meta_field gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fortimanager, and nothing reaches the server without passing your rules. This is the rule we recommend for set_object_meta_field:
{
"version": "1",
"default": "deny",
"tools": {
"set_object_meta_field": {
"limits": [
{
"counter": "set_object_meta_field_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_object_meta_field 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.
Free to start. No card required.
set_object_meta_field. 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 set_object_meta_field: 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.
set_object_meta_field 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 set_object_meta_field 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 set_object_meta_field. 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.
set_object_meta_field 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.
Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
584 Fortimanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.