AI agents call search_devices_by_class 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.
Search and filtering operations that retrieve device information without modifying state are read operations. The tool appears to query devices by their classification attribute, consistent with other non-destructive HomeyPro information retrieval tools.
From the tool's definition Tool name 'search_devices_by_class' indicates a search/query operation. No description provided, but the naming convention aligns with sibling read-only tools like 'get_device', 'get_devices_capabilities', and 'get_devices_classes' on the same HomeyPro server.
Documented attack patterns abuse exactly the kind of access search_devices_by_class 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 search_devices_by_class:
{
"version": "1",
"default": "deny",
"tools": {
"search_devices_by_class": {}
}
}search_devices_by_class 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.
search_devices_by_class. 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 search_devices_by_class: 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.
search_devices_by_class 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 search_devices_by_class 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 search_devices_by_class. 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.
search_devices_by_class 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.