Manually trigger the Reflector agent to compress and consolidate observations.
AI agents invoke reflect to trigger actions in Codewatch Memory. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This is classified as Execute rather than Write because it triggers an autonomous agent process whose exact effects depend on the agent's logic and the current state of observations—similar to running a script or batch operation. The severity is medium because while it modifies stored data, the modifications are reversible (observations are compressed, not deleted) and confined to a single project's memory store.
From the tool's definition The tool 'reflect' manually triggers the Reflector agent to perform compression and consolidation of observations stored in the SQLite database.
Attacks that exploit this kind of access
Manually trigger the Reflector agent to compress and consolidate observations. It is categorised as a Execute tool in the Codewatch Memory MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Codewatch Memory MCP server in PolicyLayer and add a rule for reflect: 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 Codewatch Memory. Nothing to install.
reflect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the reflect 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 reflect. 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.
reflect is provided by the Codewatch Memory MCP server (klausandrade/codewatch). 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 →