Filtered list of raw tracking entries. Useful for digging into specific projects, tags, or finding what window titles appeared. When a period is set, respects the same dashboard exclusions stored in SQLite (ignored apps/projects/breakdown patterns, days_filter) plus optional hour/device filters s...
AI agents call query_entries 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 performs data retrieval only. While it accesses detailed time-tracking information including window titles and activity logs, which could be sensitive, the read-only nature and lack of side effects place it in the Read category.
From the tool's definition Tool description explicitly states 'Filtered list of raw tracking entries' and is part of a 'read-only Model Context Protocol server.' It retrieves time-tracking data from a local SQLite database without modification capabilities.
Attacks that exploit this kind of access
Filtered list of raw tracking entries. Useful for digging into specific projects, tags, or finding what window titles appeared. When a period is set, respects the same dashboard exclusions stored in SQLite (ignored apps/projects/breakdown patterns, days_filter) plus optional hour/device filters so aggregates stay consistent with Charts; omit period to bypass those scope rules while still filtering by tag/app/search/etc. Defaults to active foreground entries only — pass mode=. 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 query_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 Vetroscope MCP. Nothing to install.
query_entries 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 query_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.
Set action: deny in the PolicyLayer policy for query_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.
query_entries 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 →