get_object_metadata
A read tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/get-object-metadata.md
What get_object_metadata does on Fortimanager
AI agents call get_object_metadata 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.
Why get_object_metadata is rated Low
The name strongly suggests this tool retrieves metadata about objects without modifying state. 'Get' operations are typically read-only queries with no side effects. Given the empty description, confidence is moderate but the naming pattern is clear enough to classify as Read rather than higher-severity categories. Low severity because metadata retrieval has minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name 'get_object_metadata' indicates a retrieval operation. The 'get_' prefix conventionally denotes read-only data fetching. Description is empty, limiting certainty.
Attacks that exploit this kind of access
The rule that runs get_object_metadata 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 get_object_metadata, this is the rule to start with:
get_object_metadata is read-only, so it stays allowed. 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 get_object_metadata call is checked against it from then on.
Questions about get_object_metadata
get_object_metadata 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.
Register the Fortimanager MCP server in PolicyLayer and add a rule for get_object_metadata: 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_metadata 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_metadata 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_metadata. 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_metadata 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