Get Last.fm user profile information and listening statistics - REQUIRES AUTHENTICATION for private profiles
AI agents call get_user_info 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 profile data and listening statistics without modifying, deleting, or executing operations. It has minimal blast radius—exposure would leak user music taste and history, not enable financial harm or destructive actions. Low severity due to informational nature of data retrieved.
From the tool's definition Tool name 'get_user_info' and description 'Get Last.fm user profile information and listening statistics' indicate data retrieval only. The note 'REQUIRES AUTHENTICATION for private profiles' confirms access control but no modification occurs.
Documented attack patterns abuse exactly the kind of access get_user_info 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_user_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_info": {}
}
}get_user_info 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 Last.fm user profile information and listening statistics - REQUIRES AUTHENTICATION for private profiles. 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_user_info: 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_user_info 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_user_info 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_user_info. 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_user_info 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.