Low Risk

get_weekly_track_chart

Get track listening data for a specific time period - REQUIRES AUTHENTICATION. Perfect for temporal queries like

How to control get_weekly_track_chart ↓

AI agents call get_weekly_track_chart 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.

Low Risk

This is a straightforward data query that retrieves temporal listening history from Last.fm. While it requires authentication to access personal data, the operation itself is read-only and returns information without any capability to modify, delete, or execute external operations. The 'blast radius' is limited to information disclosure of the user's own music listening patterns, posing minimal risk.

From the tool's definition Tool name 'get_weekly_track_chart' and description 'Get track listening data for a specific time period' indicate data retrieval with no modification, creation, or deletion. The tool fetches historical listening statistics without side effects.

Documented attack patterns abuse exactly the kind of access get_weekly_track_chart 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_weekly_track_chart:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_weekly_track_chart": {}
  }
}

get_weekly_track_chart is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Lastfm — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_weekly_track_chart tool do? +

Get track listening data for a specific time period - REQUIRES AUTHENTICATION. Perfect for temporal queries like. It is categorised as a Read tool in the Lastfm MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_weekly_track_chart? +

Register the Lastfm MCP server in PolicyLayer and add a rule for get_weekly_track_chart: 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.

What risk level is get_weekly_track_chart? +

get_weekly_track_chart is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_weekly_track_chart? +

Yes. Add a rate_limit block to the get_weekly_track_chart 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.

How do I block get_weekly_track_chart completely? +

Set action: deny in the PolicyLayer policy for get_weekly_track_chart. 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.

What MCP server provides get_weekly_track_chart? +

get_weekly_track_chart 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.

Enforce policy on every Lastfm tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.