This record as markdown: /tools/ruflo/iot-custody-epoch.md
What iot_custody_epoch does on Ruflo
AI agents call iot_custody_epoch to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why iot_custody_epoch is rated Low
This tool retrieves a custody epoch value, which is a data query operation with no capability to modify, execute, or delete anything. The minimal description and generic nature of 'custody epoch' in an IoT/agent swarm context suggests it returns status or metadata. Classified as Read with low severity due to limited blast radius if misused by an agent.
From the tool's definition Tool name 'iot_custody_epoch' with description 'Get custody epoch' indicates a retrieval operation. The verb 'Get' explicitly signals a read-only query with no side effects.
Attacks that exploit this kind of access
The rule that runs iot_custody_epoch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every iot_custody_epoch call is checked against it from then on.
Questions about iot_custody_epoch
Get custody epoch. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo 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 Ruflo. 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 Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue