This record as markdown: /tools/ruflo/feedback-record.md
What feedback_record does on Ruflo
AI agents use feedback_record 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.
Why feedback_record is rated Medium
The tool records feedback entries into what appears to be a learning/memory system. This is a write operation that creates new data. It could influence agent behavior over time (self-learning swarm intelligence), which elevates severity slightly, but the action itself is reversible in principle. No indication of code execution, deletion, or financial operations.
From the tool's definition 'Record feedback for learning' — creates/stores new feedback data in the system
Attacks that exploit this kind of access
The rule that runs feedback_record 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 feedback_record, this is the rule to start with:
feedback_record 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every feedback_record call is checked against it from then on.
Questions about feedback_record
Record feedback for learning. 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 feedback_record: 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.
feedback_record 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 feedback_record 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 feedback_record. 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.
feedback_record 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