AI agents call firewalla_get_alarm to retrieve information from Firewalla without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data about a single alarm without modifying, deleting, or executing any actions. It is a pure query/fetch operation consistent with the read-only nature of the Firewalla MCP server. The incomplete description does not alter this classification—the name and server context clearly indicate a retrieval function with no side effects.
From the tool's definition Tool name 'firewalla_get_alarm' fetches alarm details; server is explicitly described as 'read-only' and 'without making any changes'; sibling tools (list_*, search_*, get_*) are all read operations.
Attacks that exploit this kind of access
Fetch the full detail of a single alarm by \. It is categorised as a Read tool in the Firewalla MCP Server, which means it retrieves data without modifying state.
Register the Firewalla MCP server in PolicyLayer and add a rule for firewalla_get_alarm: 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 Firewalla. Nothing to install.
firewalla_get_alarm 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 firewalla_get_alarm 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 firewalla_get_alarm. 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.
firewalla_get_alarm is provided by the Firewalla MCP server (productengineered/firewalla-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →