AI agents call get_object_type_option_attributes to retrieve information from Fortimanager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix strongly suggests this is a read operation that retrieves or queries attribute information about object types and their options. No description is provided, but the naming pattern is consistent with Read category tools (get, fetch, list, query). The blast radius of retrieving configuration attribute metadata is low, as no data is modified, deleted, or executed.
From the tool's definition Tool name contains 'get_object_type_option_attributes' with 'get' prefix, indicating a retrieval operation. Description is empty, limiting definitive assessment.
Documented attack patterns abuse exactly the kind of access get_object_type_option_attributes 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 get_object_type_option_attributes:
{
"version": "1",
"default": "deny",
"tools": {
"get_object_type_option_attributes": {}
}
}get_object_type_option_attributes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_object_type_option_attributes. It is categorised as a Read tool in the Fortimanager MCP Server, which means it retrieves data without modifying state.
Register the Fortimanager MCP server in PolicyLayer and add a rule for get_object_type_option_attributes: 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.
get_object_type_option_attributes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_object_type_option_attributes 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 get_object_type_option_attributes. 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.
get_object_type_option_attributes 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.