iot_store_query

Query device vector store

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/iot-store-query.md

WHAT IT DOES

What iot_store_query does on Claude Flow

AI agents call iot_store_query to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why iot_store_query is rated Low

The tool performs a query operation on a vector store, which is fundamentally a read-only data retrieval action. Vector store queries retrieve or search existing data without creating, modifying, deleting, or executing external operations. The 'query' verb combined with 'device vector store' context confirms this is a Read category tool with minimal risk.

From the tool's definition Tool name 'iot_store_query' and description 'Query device vector store' indicate a retrieval/query operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs iot_store_query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For iot_store_query, this is the rule to start with:

iot_store_query Allowed

iot_store_query is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "iot_store_query": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every iot_store_query call is checked against it from then on.

FAQ

Questions about iot_store_query

What does the iot_store_query tool do? +

Query device vector store. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on iot_store_query? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for iot_store_query: 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.

What risk level is iot_store_query? +

iot_store_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit iot_store_query? +

Yes. Add a rate_limit block to the iot_store_query 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.

How do I block iot_store_query completely? +

Set action: deny in the PolicyLayer policy for iot_store_query. 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.

What MCP server provides iot_store_query? +

iot_store_query 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.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →