dsh-tool-quota

When an agent is handed a search tool, each individual call is perfectly legal. That does nothing to stop it from firing off eighty queries in a single session or pulling back a four-megabyte page and dumping the whole thing into the conversation. dsh-tool-quota closes that gap by enforcing hard caps on both call count and result byte size, scoped per tool and per session.

Two design choices stand out. First, over-quota results are discarded outright rather than truncated: the call fails with a machine-readable code (TOOL_QUOTA_CALLS or TOOL_QUOTA_BYTES), so a caller can branch on the error without parsing prose. Second, the quota is a session-level total, not a rate limiter: there is no time window, no sleep-and-retry, and the allowance does not refill until the session ends or the plugin is reloaded. The plugin also registers a tool_quota_status tool that lets an agent proactively check the remaining allowance for every configured tool, removing the need to discover the cap by hitting it.

It fits developers deploying multi-tool agent workflows who need to prevent any single tool from being over-invoked. The plugin deliberately does not handle spend budgets, token accounting, or permission gating. It does one thing: give every tool a clear per-session usage ceiling and a clear, coded signal when that ceiling is crossed.