Get custody epoch
AI agents call iot_custody_epoch 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 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
Get custody epoch. 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_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.
iot_custody_epoch 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_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.
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.
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.