Dense per-day series of active and passive seconds for a period. Default period is
AI agents call get_calendar 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 queries time-tracking data from a local SQLite database and returns calendar information without side effects. It is a retrieval operation consistent with Read category tools. Low severity because it accesses only time-tracking metadata with no ability to modify data, execute commands, or affect external systems.
From the tool's definition Server explicitly described as 'read-only' and tool name 'get_calendar' retrieves 'per-day series of active and passive seconds' — a query operation with no modifications, deletions, or execution capabilities.
Attacks that exploit this kind of access
Dense per-day series of active and passive seconds for a period. Default period is. 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_calendar: 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_calendar 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_calendar 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_calendar. 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_calendar 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 →