Continuous activity blocks reconstructed from the raw 30s entries — the natural grain for
AI agents call get_sessions 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 time-tracking session data from a local SQLite database without any write, execute, or destructive capabilities. It is purely informational, querying historical activity data. The read-only nature of the server and the passive data retrieval function classify it as a Read operation with low severity, as misuse would only expose personal time-tracking information already stored locally.
From the tool's definition Tool name 'get_sessions' and server description 'read-only Model Context Protocol server' that 'provides LLMs with detailed time-tracking data'. The tool retrieves 'continuous activity blocks reconstructed from raw 30s entries' with no modification capability.
Attacks that exploit this kind of access
Continuous activity blocks reconstructed from the raw 30s entries — the natural grain for. 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_sessions: 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_sessions 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_sessions 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_sessions. 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_sessions 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 →