list_ssh_filter_profiles
A read tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/list-ssh-filter-profiles.md
What list_ssh_filter_profiles does on Fortimanager
AI agents call list_ssh_filter_profiles 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 list_ssh_filter_profiles is rated Low
The tool appears to retrieve or enumerate SSH filter profiles from FortiManager without modifying or deleting data. This is a read operation with minimal blast radius—an agent could discover SSH filter configuration details, but cannot alter security policies or cause irreversible damage. Classification as Read with low severity is appropriate.
From the tool's definition Tool name 'list_ssh_filter_profiles' indicates retrieval of SSH filter profile configurations. The 'list_' prefix is a standard pattern for query/retrieve operations with no side effects. Description is empty, which slightly reduces confidence.
Attacks that exploit this kind of access
The rule that runs list_ssh_filter_profiles 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 list_ssh_filter_profiles, this is the rule to start with:
list_ssh_filter_profiles 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 list_ssh_filter_profiles call is checked against it from then on.
Questions about list_ssh_filter_profiles
list_ssh_filter_profiles 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 list_ssh_filter_profiles: 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.
list_ssh_filter_profiles 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 list_ssh_filter_profiles 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 list_ssh_filter_profiles. 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.
list_ssh_filter_profiles 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