AI agents call get_loved_tracks to retrieve information from Lastfm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user-specific data (loved tracks) from Last.fm without modifying, deleting, or executing operations. It is a passive query operation that reads music preference data. The incomplete description lowers confidence slightly, but the naming pattern and context confirm it is a Read operation with low severity—misuse would only expose personal music preferences, not cause destructive or financial harm.
From the tool's definition Tool name 'get_loved_tracks' and server description indicate data retrieval from Last.fm listening history. The description 'Get user' is incomplete but aligns with querying user-specific music data.
Documented attack patterns abuse exactly the kind of access get_loved_tracks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lastfm, and nothing reaches the server without passing your rules. This is the rule we recommend for get_loved_tracks:
{
"version": "1",
"default": "deny",
"tools": {
"get_loved_tracks": {}
}
}get_loved_tracks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get user. It is categorised as a Read tool in the Lastfm MCP Server, which means it retrieves data without modifying state.
Register the Lastfm MCP server in PolicyLayer and add a rule for get_loved_tracks: 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 Lastfm. Nothing to install.
get_loved_tracks 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_loved_tracks 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_loved_tracks. 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_loved_tracks is provided by the Lastfm MCP server (rianvdm/lastfm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Lastfm tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Lastfm tools catalogued and risk-classified — across an index of 42,500+ MCP servers.