AI agents use wtf_freshell to create or update resources in Wtf — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wtf environment.
The tool archives the current incident and initializes a new journal session. Since previous entries are explicitly preserved, this is not destructive. It modifies state by closing/archiving the current incident context and creating a new one, making it a Write operation. Misuse could cause loss of active incident context mid-investigation, hence medium severity.
From the tool's definition Archive the current incident and start a fresh journal. Previous entries are preserved in the database.
Attacks that exploit this kind of access
Archive the current incident and start a fresh journal. Previous entries are preserved in the database. It is categorised as a Write tool in the Wtf MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wtf MCP server in PolicyLayer and add a rule for wtf_freshell: 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 Wtf. Nothing to install.
wtf_freshell 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 wtf_freshell 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 wtf_freshell. 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.
wtf_freshell is provided by the Wtf MCP server (wave-engineering/mcp-server-wtf). 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 →