whooing_bulk_add_entries · Whooing MCP: Risk & Policy

WHAT IT DOES

What whooing_bulk_add_entries does on Whooing MCP

AI agents use whooing_bulk_add_entries 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_bulk_add_entries needs a policy

This tool creates (writes) multiple financial transaction entries, which is a reversible modification. While it modifies financial data, it does not move money, execute arbitrary code, or irreversibly delete data. It falls under Write rather than Financial because it records transactions rather than processing payments or financial obligations.

From the tool's definition Tool name is 'whooing_bulk_add_entries' and description states 'Create multiple transaction entries in Whooing.' The verb 'Create' indicates data creation, and 'bulk' suggests potential for high-volume modifications.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

whooing_bulk_add_entries Rate-limited

whooing_bulk_add_entries 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_bulk_add_entries": {
      "limits": [
        {
          "counter": "whooing_bulk_add_entries_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_bulk_add_entries

What does the whooing_bulk_add_entries tool do? +

Create multiple transaction entries in Whooing. Use whooing_accounts first to look up account IDs. 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_bulk_add_entries? +

Register the Whooing MCP server in PolicyLayer and add a rule for whooing_bulk_add_entries: 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_bulk_add_entries? +

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

Can I rate-limit whooing_bulk_add_entries? +

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

Set action: deny in the PolicyLayer policy for whooing_bulk_add_entries. 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_bulk_add_entries? +

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