Get vector store health
AI agents call iot_store_status to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about a vector store (likely a database or cache component). The verb 'Get' and the focus on 'health' monitoring are purely observational. There is no capability to modify, execute external operations, delete data, or incur financial obligations. It is a diagnostic read operation with minimal risk.
From the tool's definition Tool name 'iot_store_status' and description 'Get vector store health' indicate a query/status check operation with no data modification or side effects.
Attacks that exploit this kind of access
Get vector store health. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for iot_store_status: 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 Claude Flow. Nothing to install.
iot_store_status 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 iot_store_status 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 iot_store_status. 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.
iot_store_status is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.