Record feedback for a specific memory entry.
AI agents use feedback to create or update resources in VecFS — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VecFS environment.
Recording feedback modifies data (annotates or updates a memory entry with feedback) but is reversible and has limited blast radius. It does not delete, execute code, or involve financial operations.
From the tool's definition "Record feedback for a specific memory entry" — creates/updates a feedback record associated with an existing memory
Documented attack patterns abuse exactly the kind of access feedback gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VecFS, and nothing reaches the server without passing your rules. This is the rule we recommend for feedback:
{
"version": "1",
"default": "deny",
"tools": {
"feedback": {
"limits": [
{
"counter": "feedback_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}feedback 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.
Free to start. No card required.
Record feedback for a specific memory entry. It is categorised as a Write tool in the VecFS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VecFS MCP server in PolicyLayer and add a rule for feedback: 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 VecFS. Nothing to install.
feedback 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 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. 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 is provided by the VecFS MCP server (wazzamo/vecfs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VecFS, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 VecFS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.