List the user
AI agents call list_tags 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 tag data without modifying, deleting, or executing anything. It fits the 'Read' category as it queries or lists data from a local SQLite database. Severity is low because tag enumeration is low-risk data retrieval with no side effects. Confidence is high (0.9) based on the explicit read-only server design, though the tool description is truncated and uninformative.
From the tool's definition Tool name is 'list_tags' and server description explicitly states it is a 'read-only' MCP server that 'provides LLMs with detailed time-tracking data.' The tool description appears incomplete ('List the user') but given the server's read-only nature and the…
Attacks that exploit this kind of access
List the user. 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 list_tags: 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.
list_tags 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 list_tags 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 list_tags. 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.
list_tags 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 →