AI agents call get_flows_by_folder 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 flows organized by folder without modifying, executing, or deleting anything. The 'get_' prefix and sibling naming conventions confirm it is a read operation. While confidence is slightly reduced due to the empty description, the naming pattern and API context strongly indicate a query/retrieval function with no side effects.
From the tool's definition Tool name 'get_flows_by_folder' indicates a retrieval operation. The description is empty, but the name and context of sibling tools (get_flows_without_folder, get_device, get_metrics, etc.) all follow a 'get_*' pattern typical of read-only query operations…
Documented attack patterns abuse exactly the kind of access get_flows_by_folder 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_flows_by_folder:
{
"version": "1",
"default": "deny",
"tools": {
"get_flows_by_folder": {}
}
}get_flows_by_folder 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_flows_by_folder. 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_flows_by_folder: 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_flows_by_folder 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_flows_by_folder 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_flows_by_folder. 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_flows_by_folder 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.