AI agents call trw_surface_diff to retrieve information from Trw without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A diff operation computes and returns the differences between two snapshots without modifying any data. This is a read/query operation. Severity is low as misuse would only expose comparison data. Confidence is slightly reduced because 'surface snapshots' is not fully explained, but diffing is universally a read operation.
From the tool's definition Structured diff between two surface snapshots
Attacks that exploit this kind of access
Structured diff between two surface snapshots. It is categorised as a Read tool in the Trw MCP Server, which means it retrieves data without modifying state.
Register the Trw MCP server in PolicyLayer and add a rule for trw_surface_diff: 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_surface_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the trw_surface_diff 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_surface_diff. 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_surface_diff 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 →