AI agents call get_service_where_used 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 tool name contains the 'get' verb pattern typical of read operations (query, retrieve data). The absence of verbs like 'create', 'delete', 'execute', or 'modify' suggests it performs a lookup or retrieval operation. However, confidence is moderate due to the empty description which prevents verification of the actual implementation and potential side effects.
From the tool's definition Tool name 'get_service_where_used' suggests querying/retrieving information about where a service is used, with no modification indicated. No description provided to confirm.
Documented attack patterns abuse exactly the kind of access get_service_where_used 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_service_where_used:
{
"version": "1",
"default": "deny",
"tools": {
"get_service_where_used": {}
}
}get_service_where_used 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_service_where_used. 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_service_where_used: 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_service_where_used 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_service_where_used 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_service_where_used. 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_service_where_used 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.