Rolls up app totals into broad categories (editor, browser, adobe, communication, gaming, productivity, creative, music_creation, etc.) so you can ask
AI agents call get_category_breakdown to retrieve information from Vetroscope MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and summarizes existing time-tracking data without creating, modifying, deleting, or executing anything. It is a pure read operation on local data with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'get_category_breakdown' and description explicitly states it 'rolls up app totals into broad categories' — a retrieval and aggregation operation with no modification or execution.
Attacks that exploit this kind of access
Rolls up app totals into broad categories (editor, browser, adobe, communication, gaming, productivity, creative, music_creation, etc.) so you can ask. It is categorised as a Read tool in the Vetroscope MCP MCP Server, which means it retrieves data without modifying state.
Register the Vetroscope MCP server in PolicyLayer and add a rule for get_category_breakdown: 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 Vetroscope MCP. Nothing to install.
get_category_breakdown 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_category_breakdown 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_category_breakdown. 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_category_breakdown is provided by the Vetroscope MCP server (rankin-works/vetroscope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →