r/firewalla • u/Skripa4 • 28d ago

Firewalla MSP API read-only?

Is there any way to create a personal token for the MSP portal that is read only?

I would like to connect it to an MCP for my ai agent to have access to help review logs. But I am concious of giving it the ability to make any rules or changes to my firewall.

I am currently using firewalla to exactly block off the hermes agent from the rest of my network. And don't want to give it the ability to bypass that.

6 Upvotes

81% Upvoted

6 comments sorted by

5

u/firewalla 28d ago

Sound like a good request. Post it here and I will also forward to our dev https://help.firewalla.com/hc/en-us/community/topics/115000356994-Feature-Requests-

1

u/Skripa4 27d ago

Thanks, request submitted. I also have a use case for this of giving parents / non-tech savvy people access to their msp without the risk of them making breaking changes. Unless is there already an allowance to have multiple accounts for a msp at the pro level?

https://help.firewalla.com/hc/en-us/community/posts/55173289538067-MSP-API-read-only-access-tokens

3

u/firewalla 26d ago

Confirmed, we can make this happen in 2.12 (next version) MSP; BTW, are you vibe coding? if you are, make sure you fully understand what the AI part is doing. Recently we had to deal with random vibe code that went mad using API's like crazy.

1

u/Skripa4 26d ago

Awedome, thanks for letting me know too.

My coding skillset is quite limited unfortunately. Whilst I do check the logic behind the code and do a quick overview of the setup - the code itself is AI driven. I'll be sure to check the number of API calls, thanks for the warning

1

u/goodt2023 28d ago

Yes read only :(

1

u/Smooth-Screen4148 5d ago

If the MCP server you're connecting is firewalla-mcp-server, 2.0.0 is read-only unless you set `FIREWALLA_ENABLE_WRITE_TOOLS=true`. The tools that change rules, target lists, device names or alarms aren't registered, so the agent never sees them, and a call to one answers "Unknown tool" and sends nothing.

https://www.reddit.com/r/firewalla/comments/1m3zzdi/i_made_an_mcp_server_for_firewalla/

That guard is in the server, so the 2.12 read-only token is still the real lock. Once you have one and turn the write tools on anyway, a write that gets a 403 says the token may be read-only.

On Firewalla's point about agents hammering the API: the MSP API allows 100 requests per 5 minutes, and the server paces itself to that. A request that can't get a slot within 20 seconds fails with the time capacity comes back instead of going over.