iot_custody_epoch

Get custody epoch

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-custody-epoch.md

WHAT IT DOES

What iot_custody_epoch does on Claude Flow

AI agents call iot_custody_epoch 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_custody_epoch is rated Low

This tool retrieves metadata (a custody epoch value) from an IoT system. There are no side effects, state changes, or external operations triggered. Retrieving a timestamp or epoch counter is a read-only operation with minimal blast radius even if misused.

From the tool's definition Tool name 'iot_custody_epoch' with description 'Get custody epoch' indicates a retrieval operation. The verb 'Get' and the absence of any modification, deletion, or execution language suggest a query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs iot_custody_epoch 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_custody_epoch, this is the rule to start with:

iot_custody_epoch Allowed

iot_custody_epoch 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_custody_epoch": {}
  }
}

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_custody_epoch call is checked against it from then on.

FAQ

Questions about iot_custody_epoch

What does the iot_custody_epoch tool do? +

Get custody epoch. 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_custody_epoch? +

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

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

Can I rate-limit iot_custody_epoch? +

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

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

iot_custody_epoch 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

The MCP Attack Database →

Guides

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