Get all sprinkler systems
AI agents call get_sprinkler_systems to retrieve information from HC3 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 information about sprinkler systems in a Fibaro HC3 smart home setup. It performs a read-only operation that queries existing data without creating, modifying, deleting, or executing any actions. There is no financial impact, no destructive capability, and no code execution.
From the tool's definition Tool name 'get_sprinkler_systems' and description 'Get all sprinkler systems' indicate a query/retrieval operation with no side effects or data modification.
Attacks that exploit this kind of access
Get all sprinkler systems. It is categorised as a Read tool in the HC3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for get_sprinkler_systems: 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 HC3 MCP Server. Nothing to install.
get_sprinkler_systems 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_sprinkler_systems 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_sprinkler_systems. 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_sprinkler_systems is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_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 →