Get firewall configuration and rules for a site, including ACL rules, IP groups, and security policies.
AI agents call getFirewallSetting to retrieve information from Tplink Omada without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves firewall configuration, ACL rules, IP groups, and security policies. While it is fundamentally a Read operation with no side effects, the sensitivity of firewall configuration data and security policies warrants a medium severity rating due to potential information disclosure risks if accessed by an unauthorized agent. The tool itself performs no destructive, write, execute, or financial actions.
From the tool's definition Tool name 'getFirewallSetting' uses 'get' verb indicating retrieval. Description states 'Get firewall configuration and rules' — a read-only operation that retrieves existing firewall settings without modification.
Documented attack patterns abuse exactly the kind of access getFirewallSetting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tplink Omada, and nothing reaches the server without passing your rules. This is the rule we recommend for getFirewallSetting:
{
"version": "1",
"default": "deny",
"tools": {
"getFirewallSetting": {}
}
}getFirewallSetting 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 firewall configuration and rules for a site, including ACL rules, IP groups, and security policies. It is categorised as a Read tool in the Tplink Omada MCP Server, which means it retrieves data without modifying state.
Register the Tplink Omada MCP server in PolicyLayer and add a rule for getFirewallSetting: 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 Tplink Omada. Nothing to install.
getFirewallSetting 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 getFirewallSetting 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 getFirewallSetting. 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.
getFirewallSetting is provided by the Tplink Omada MCP server (migueltvms/tplink-omada-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tplink Omada, 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.
327 Tplink Omada tools catalogued and risk-classified — across an index of 43,000+ MCP servers.