Report whether a recommended tool worked or not. This closes the learning loop — the Unfragile graph uses this feedback to improve future recommendations. Call this after trying a tool from search results.
AI agents use feedback to create or update resources in Unfragile — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unfragile environment.
This tool writes feedback data back to the system to influence future recommendations. It creates/updates records in the learning system, making it a Write operation. It is reversible in the sense that individual feedback entries could be corrected, and the blast radius is low since misuse would only skew recommendations slightly rather than causing destructive or financial harm.
From the tool's definition 'Report whether a recommended tool worked or not' and 'the Unfragile graph uses this feedback to improve future recommendations' — submits feedback data that modifies the recommendation graph
Attacks that exploit this kind of access
Report whether a recommended tool worked or not. This closes the learning loop — the Unfragile graph uses this feedback to improve future recommendations. Call this after trying a tool from search results. It is categorised as a Write tool in the Unfragile MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unfragile 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 Unfragile. 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 Unfragile MCP server (savirinc/unfragile-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →