whooing_update_entry · Whooing MCP: Risk & Policy

WHAT IT DOES

What whooing_update_entry does on Whooing MCP

AI agents use whooing_update_entry to create or update resources in Whooing MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Whooing MCP environment.

WHY IT NEEDS A POLICY

Why whooing_update_entry needs a policy

This tool modifies existing financial transaction entries, which is a reversible write operation. While it affects financial data, it does not move money or create financial obligations directly (category: Financial), nor does it delete data irreversibly (category: Destructive).

From the tool's definition Tool name 'whooing_update_entry' and description 'Update an existing transaction entry in Whooing' indicate modification of financial data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

whooing_update_entry Rate-limited

whooing_update_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": {
    "whooing_update_entry": {
      "limits": [
        {
          "counter": "whooing_update_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 Whooing MCP, so you can run agents against it safely.

FAQ

Questions about whooing_update_entry

What does the whooing_update_entry tool do? +

Update an existing transaction entry in Whooing. It is categorised as a Write tool in the Whooing MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on whooing_update_entry? +

Register the Whooing MCP server in PolicyLayer and add a rule for whooing_update_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 Whooing MCP. Nothing to install.

What risk level is whooing_update_entry? +

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

Can I rate-limit whooing_update_entry? +

Yes. Add a rate_limit block to the whooing_update_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 whooing_update_entry completely? +

Set action: deny in the PolicyLayer policy for whooing_update_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 whooing_update_entry? +

whooing_update_entry is provided by the Whooing MCP server (jmjeong/whooing-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.