iot_store_ingest · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What iot_store_ingest does on Claude Flow

AI agents use iot_store_ingest to create or update resources in Claude Flow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.

WHY IT NEEDS A POLICY

Why iot_store_ingest needs a policy

Ingesting vectors into a store is a write operation: it creates new data entries in the IoT device store. It does not appear to delete or overwrite existing data irreversibly, nor does it execute code or move money. Medium severity because bulk vector ingestion could corrupt or pollute a device data store if misused, but the operation is generally reversible by deleting the ingested records.

From the tool's definition 'Ingest vectors into device store' — creates/inserts vector data into a device store

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

iot_store_ingest Rate-limited

iot_store_ingest stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "iot_store_ingest": {
      "limits": [
        {
          "counter": "iot_store_ingest_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Flow, so you can run agents against it safely.

FAQ

Questions about iot_store_ingest

What does the iot_store_ingest tool do? +

Ingest vectors into device store. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on iot_store_ingest? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for iot_store_ingest: 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_ingest? +

iot_store_ingest is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit iot_store_ingest? +

Yes. Add a rate_limit block to the iot_store_ingest 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_ingest completely? +

Set action: deny in the PolicyLayer policy for iot_store_ingest. 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_ingest? +

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