AI agents use trw_submit_feedback to create or update resources in Trw — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trw environment.
The 'submit' verb strongly suggests the tool creates or posts feedback records to persistent storage (consistent with the server's engineering memory goal), making it a Write action. This could reversibly modify stored feedback or learnings. Without a description, severity is estimated as medium—the tool likely affects engineering memory rather than critical systems, and feedback submission is generally reversible.
From the tool's definition Tool name 'trw_submit_feedback' contains 'submit', which indicates creation or modification of feedback data. The description is empty, limiting confidence in exact behavior.
Attacks that exploit this kind of access
trw_submit_feedback. It is categorised as a Write tool in the Trw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trw MCP server in PolicyLayer and add a rule for trw_submit_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 Trw. Nothing to install.
trw_submit_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 trw_submit_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 trw_submit_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.
trw_submit_feedback is provided by the Trw MCP server (wallter/trw-mcp). 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 →