classify_entry · Wtf MCP: Risk & Policy

WHAT IT DOES

What classify_entry does on Wtf

AI agents use classify_entry 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.

WHY IT NEEDS A POLICY

Why classify_entry needs a policy

The tool writes a classification back to the SQLite database for a given log entry. 'Classify' implies updating/labeling an existing record, which is a reversible write operation. No code execution, deletion, or financial action is implied. Confidence is moderate because the description is sparse and doesn't detail exactly what fields are written or whether it triggers further side effects.

From the tool's definition Classify a troubleshooting log entry

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

classify_entry Rate-limited

classify_entry stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "classify_entry": {
      "limits": [
        {
          "counter": "classify_entry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Wtf, so you can run agents against it safely.

FAQ

Questions about classify_entry

What does the classify_entry tool do? +

Classify a troubleshooting log entry. 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.

How do I enforce a policy on classify_entry? +

Register the Wtf MCP server in PolicyLayer and add a rule for classify_entry: 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.

What risk level is classify_entry? +

classify_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit classify_entry? +

Yes. Add a rate_limit block to the classify_entry 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.

How do I block classify_entry completely? +

Set action: deny in the PolicyLayer policy for classify_entry. 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.

What MCP server provides classify_entry? +

classify_entry 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.