AI agents call get_flow_folders to retrieve information from HomeyPro MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about flow folder organization within a HomeyPro system. It performs no side effects, does not execute any actions, and does not modify state. The operation is purely informational, consistent with list/query operations in the Read category. Blast radius is minimal—data exposure could inform an attacker about automation structure, but no destructive or operational harm is possible.
From the tool's definition Tool name 'get_flow_folders' and description 'Get all flow folders' indicate a retrieval operation with no modification or execution capability. The verb 'Get' and context of querying folder structures are characteristic of read-only operations.
Documented attack patterns abuse exactly the kind of access get_flow_folders gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HomeyPro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_flow_folders:
{
"version": "1",
"default": "deny",
"tools": {
"get_flow_folders": {}
}
}get_flow_folders 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 all flow folders. It is categorised as a Read tool in the HomeyPro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HomeyPro MCP Server MCP server in PolicyLayer and add a rule for get_flow_folders: 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 HomeyPro MCP Server. Nothing to install.
get_flow_folders 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_flow_folders 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_flow_folders. 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_flow_folders is provided by the HomeyPro MCP Server MCP server (pigmej/python-homey-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HomeyPro MCP Server, 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.
19 HomeyPro MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.