Lists canonical deep-links Vetroscope captured for media the user actually played — Spotify
AI agents call get_media_links 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 historical data about media links from a read-only time-tracking database. It queries existing records without creating, modifying, deleting, or executing any operations. The blast radius is minimal—exposure of Spotify links or listening history poses privacy concerns but no operational risk.
From the tool's definition Tool name 'get_media_links' and description 'Lists canonical deep-links Vetroscope captured for media the user actually played' indicate a retrieval operation. Server description explicitly states 'read-only' access to local SQLite data.
Attacks that exploit this kind of access
Lists canonical deep-links Vetroscope captured for media the user actually played — Spotify. 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_media_links: 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_media_links 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_media_links 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_media_links. 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_media_links 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 →