get_entry_count
Count entries in a workspace (workspace_id or workspace_slug) with optional device/host/method/status/search filters.
This record as markdown: /tools/dev-busymate-busymate-devtools/get-entry-count.md
What get_entry_count does on Busymate DevTools
AI agents call get_entry_count to retrieve information from Busymate DevTools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
after | string | — | |
hosts | array | — | |
before | string | — | |
origin | string | — | |
methods | array | — | |
search_q | string | — | |
device_uuids | array | — | |
status_class | number | — | |
workspace_id | string | — | |
workspace_slug | string | — |
Parameters from the server's own tool schema.
Why get_entry_count is rated Low
This tool retrieves a metric (entry count) from existing data in a workspace. It accepts filters (device, host, method, status, search) to narrow the query, but performs no mutations, deletions, or external operations. It is a simple read/query operation appropriate for inspecting captured traffic metadata in a debugging tool context.
From the tool's definition Tool description states it 'Count[s] entries in a workspace' with filtering options. The verb 'count' and the absence of any write, delete, or execute keywords indicate a data retrieval operation with no side effects.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs get_entry_count safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Busymate DevTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_entry_count, this is the rule to start with:
get_entry_count is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Busymate DevTools, apply this rule, and every get_entry_count call is checked against it from then on.
Questions about get_entry_count
Count entries in a workspace (workspace_id or workspace_slug) with optional device/host/method/status/search filters. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
get_entry_count accepts 10 parameters: after, hosts, before, origin, methods, search_q, device_uuids, status_class, workspace_id, workspace_slug. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools MCP server in PolicyLayer and add a rule for get_entry_count: 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 Busymate DevTools. Nothing to install.
get_entry_count is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_entry_count 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 get_entry_count. 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.
get_entry_count is provided by the Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue