AI agents use hooks_intelligence_trajectory-step to create or update resources in Ruflo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ruflo environment.
The tool records (writes) a data point into a trajectory log used for reinforcement learning. This is a Write operation as it creates/appends data reversibly. It does not delete, execute code directly, or involve financial transactions. Severity is medium because misuse could corrupt RL training data or manipulate agent learning trajectories, but it is unlikely to cause immediate irreversible harm.
From the tool's definition 'Record step in trajectory for reinforcement learning' — the tool writes/persists a trajectory step entry into a data store for RL purposes
Attacks that exploit this kind of access
Record step in trajectory for reinforcement learning Use when native Bash hooks (via Claude Code\. It is categorised as a Write tool in the Ruflo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ruflo MCP server in PolicyLayer and add a rule for hooks_intelligence_trajectory-step: 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.
hooks_intelligence_trajectory-step is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hooks_intelligence_trajectory-step 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 hooks_intelligence_trajectory-step. 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.
hooks_intelligence_trajectory-step 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.
hooks_intelligence_trajectory-step is one line of Ruflo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →